[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil updated AS7-6334:
-----------------------------
Description:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups (OK)
clustering/infinispan
cmp
configadmin
connector
deployment-scanner
ee
ee-deployment
ejb3
jacorb
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx (OK)
jpa
jsf
jsr77 - nothing to do, empty subsystem
logging
mail
messaging [OK]
modcluster
naming
osgi (OK)
pojo - nothing to do, empty subsystem
remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts
was:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups (OK)
clustering/infinispan
cmp
configadmin
connector
deployment-scanner
ee
ee-deployment
ejb3
jacorb
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx (OK)
jpa
jsf
jsr77 - nothing to do, empty subsystem
logging
mail
messaging - PR https://github.com/jbossas/jboss-as/pull/3887
modcluster
naming
osgi (OK)
pojo - nothing to do, empty subsystem
remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts
> Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6334
> URL: https://issues.jboss.org/browse/AS7-6334
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> Task to track the work we've all been doing on expressions/transformers.
> See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
> 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
> 2) Basic transformation testing against 7.1.2 and 7.1.3
> 3) Reject-expression testing against 7.1.2 and 7.1.3
> Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
> Please edit this description and put an OK after the subsystem name to indicate it's good to go.
> clustering/jgroups (OK)
> clustering/infinispan
> cmp
> configadmin
> connector
> deployment-scanner
> ee
> ee-deployment
> ejb3
> jacorb
> jaxr OK
> jaxrs - nothing to do, empty subsystem
> jdr - nothing to do, empty subsystem
> jmx (OK)
> jpa
> jsf
> jsr77 - nothing to do, empty subsystem
> logging
> mail
> messaging [OK]
> modcluster
> naming
> osgi (OK)
> pojo - nothing to do, empty subsystem
> remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
> sar - nothing to do, empty subsystem
> security
> threads
> transactions (just needs AS7-6336)
> web
> webservices
> weld - nothing to do, empty subsystem
> xts
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-5307) Dropped connection to EJB Server from Resin Web app
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-5307?page=com.atlassian.jira.plugin.s... ]
jaikiran pai closed AS7-5307.
-----------------------------
Resolution: Done
I'm going to close this based on the reactions that I've seen in other threads similar to this one. Users have been able to get past this issue by configuring an appropriate value for the HEARTBEAT_INTERVAL, like explained in the thread in my previous reply.
> Dropped connection to EJB Server from Resin Web app
> ---------------------------------------------------
>
> Key: AS7-5307
> URL: https://issues.jboss.org/browse/AS7-5307
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Graeme Wallace
>
> From a resin web application, after opening a connection to a JBoss 7 server for EJB calls, the connection is randomly closed.
> A full worked up example is included in the forum post.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (DROOLS-15) Major problem in Rules evaluation. Can not sort Integers correctly
by John Smith (JIRA)
[ https://issues.jboss.org/browse/DROOLS-15?page=com.atlassian.jira.plugin.... ]
John Smith commented on DROOLS-15:
----------------------------------
This seems to be a bug that was introduced in 5.5.0 onwards and still exists.
This sorting code works fine with 5.4.0.
Workaround:
Instead of:
"not Number(intValue < $number.intValue)"
If you use:
"not Number(intValue() < $number.intValue)"
Then it works.
A non-getter method without telling that it is a function seems to create a problem.
A debilitating problem that reduces the confidence in the product.
I personally vote that this problem be fixed.
> Major problem in Rules evaluation. Can not sort Integers correctly
> ------------------------------------------------------------------
>
> Key: DROOLS-15
> URL: https://issues.jboss.org/browse/DROOLS-15
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: John Smith
> Assignee: Mark Proctor
> Priority: Blocker
>
> This sample is given in the drools documentation http://docs.jboss.org/drools/release/5.5.0.Final/drools-expert-docs/html_.... This drool rule is expected to sort integers. I just changed the numbers from what are given in the sample and they do not get sorted as expected. Tried using drools version 5.5.0, 5.5.1 and the master 6.0.0, but got the same wrong results.
> Following is the main code:
> package com.sample;
> public class Example2 {
> public static void main(String[] args) throws Exception {
> Number[] numbers = new Number[] { wrap(5), wrap(6), wrap(4), wrap(1), wrap(2) };
> new RuleRunner().runRules(new String[] { "Example3.drl" }, numbers);
> }
> private static Integer wrap(int i) {
> return new Integer(i);
> }
> }
> The RuleRunner class is the same as given in the example and I do not think I should give that here, since it will clutter the question. It simply creates the KnowledgeBase, stateful session, inserts the facts as given in the 'numbers' array above and then calls fireAllRules method on the session.
> The rule file (Example3.drl) is:
> rule "Rule Sort"
> dialect "mvel"
> when
> $number : Number()
> not Number(intValue < $number.intValue)
> then
> System.out.println("Number found with value: " + $number.intValue());
> retract($number);
> end
> The output I get is as follows:
> Loading file: Example3.drl
> Inserting fact: 5
> Inserting fact: 6
> Inserting fact: 4
> Inserting fact: 1
> Inserting fact: 2
> Number found with value: 1
> Number found with value: 4
> Number found with value: 2
> Number found with value: 5
> Number found with value: 6
> Not the correct expected ascending sorted order.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-3987) Replace jboss.dist with jboss.home for testsuite and other usage
by Paul Gier (JIRA)
[ https://issues.jboss.org/browse/AS7-3987?page=com.atlassian.jira.plugin.s... ]
Paul Gier closed AS7-3987.
--------------------------
Resolution: Won't Fix
jboss.home and jboss.dist will be kept as separate properties since they can refer to different locations in a single build. I opened the issue AS7-6350 to deal with reducing the number of places where the path to the AS dist is hard coded.
> Replace jboss.dist with jboss.home for testsuite and other usage
> ----------------------------------------------------------------
>
> Key: AS7-3987
> URL: https://issues.jboss.org/browse/AS7-3987
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Build System, Test Suite
> Reporter: Paul Gier
> Assignee: Ondrej Zizka
> Fix For: 7.2.0.CR1, 7.1.4.Final (EAP)
>
>
> Currently the testsuite uses a combination of the properties jboss.dist and jboss.home to represent the path to the as7 dist directory. I don't know of any situations where these two properties would be set to different values, so we can probably remove usage of jboss.dist and just use jboss.home everywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-6350) Remove hard-coded paths to AS distribution
by Paul Gier (JIRA)
Paul Gier created AS7-6350:
------------------------------
Summary: Remove hard-coded paths to AS distribution
Key: AS7-6350
URL: https://issues.jboss.org/browse/AS7-6350
Project: Application Server 7
Issue Type: Enhancement
Components: Build System, Test Suite
Reporter: Paul Gier
Assignee: Ondrej Zizka
Fix For: 7.2.0.Alpha1
There are currently a lot of places in the arquillian and testsuite modules which contain a hard-coded path to the location of the AS distribution (build/target/jbossas). This makes it difficult to change this path when re-branding the AS.
It would be good if these could be configured to use a single POM property such as jboss.home and/or jboss.dist so that the path can be updated in a single place.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6334:
----------------------------------
Description:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups (OK)
clustering/infinispan
cmp
configadmin
connector
deployment-scanner
ee
ee-deployment
ejb3
jacorb
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx (OK)
jpa
jsf
jsr77 - nothing to do, empty subsystem
logging
mail
messaging - PR https://github.com/jbossas/jboss-as/pull/3887
modcluster
naming
osgi (OK)
pojo - nothing to do, empty subsystem
remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts
was:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups (OK)
clustering/infinispan
cmp
configadmin
connector
deployment-scanner
ee
ee-deployment
ejb3
jacorb
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx (OK)
jpa
jsf
jsr77 - nothing to do, empty subsystem
logging
mail
messaging - PR https://github.com/jbossas/jboss-as/pull/3887
modcluster
naming
osgi
pojo - nothing to do, empty subsystem
remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts
> Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6334
> URL: https://issues.jboss.org/browse/AS7-6334
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> Task to track the work we've all been doing on expressions/transformers.
> See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
> 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
> 2) Basic transformation testing against 7.1.2 and 7.1.3
> 3) Reject-expression testing against 7.1.2 and 7.1.3
> Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
> Please edit this description and put an OK after the subsystem name to indicate it's good to go.
> clustering/jgroups (OK)
> clustering/infinispan
> cmp
> configadmin
> connector
> deployment-scanner
> ee
> ee-deployment
> ejb3
> jacorb
> jaxr OK
> jaxrs - nothing to do, empty subsystem
> jdr - nothing to do, empty subsystem
> jmx (OK)
> jpa
> jsf
> jsr77 - nothing to do, empty subsystem
> logging
> mail
> messaging - PR https://github.com/jbossas/jboss-as/pull/3887
> modcluster
> naming
> osgi (OK)
> pojo - nothing to do, empty subsystem
> remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
> sar - nothing to do, empty subsystem
> security
> threads
> transactions (just needs AS7-6336)
> web
> webservices
> weld - nothing to do, empty subsystem
> xts
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6334:
----------------------------------
Description:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups (OK)
clustering/infinispan
cmp
configadmin
connector
deployment-scanner
ee
ee-deployment
ejb3
jacorb
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx (OK)
jpa
jsf
jsr77 - nothing to do, empty subsystem
logging
mail
messaging - PR https://github.com/jbossas/jboss-as/pull/3887
modcluster
naming
osgi
pojo - nothing to do, empty subsystem
remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts
was:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups (PR #3886)
clustering/infinispan
cmp
configadmin
connector
deployment-scanner
ee
ee-deployment
ejb3
jacorb
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx (PR #3886)
jpa
jsf
jsr77 - nothing to do, empty subsystem
logging
mail
messaging - PR https://github.com/jbossas/jboss-as/pull/3887
modcluster
naming
osgi
pojo - nothing to do, empty subsystem
remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts
> Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6334
> URL: https://issues.jboss.org/browse/AS7-6334
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> Task to track the work we've all been doing on expressions/transformers.
> See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
> 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
> 2) Basic transformation testing against 7.1.2 and 7.1.3
> 3) Reject-expression testing against 7.1.2 and 7.1.3
> Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
> Please edit this description and put an OK after the subsystem name to indicate it's good to go.
> clustering/jgroups (OK)
> clustering/infinispan
> cmp
> configadmin
> connector
> deployment-scanner
> ee
> ee-deployment
> ejb3
> jacorb
> jaxr OK
> jaxrs - nothing to do, empty subsystem
> jdr - nothing to do, empty subsystem
> jmx (OK)
> jpa
> jsf
> jsr77 - nothing to do, empty subsystem
> logging
> mail
> messaging - PR https://github.com/jbossas/jboss-as/pull/3887
> modcluster
> naming
> osgi
> pojo - nothing to do, empty subsystem
> remoting - PR: https://github.com/jbossas/jboss-as/pull/3882
> sar - nothing to do, empty subsystem
> security
> threads
> transactions (just needs AS7-6336)
> web
> webservices
> weld - nothing to do, empty subsystem
> xts
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-6341) EJB2 CMP - 'JBAS014172: Instance not found in cache' after remove and recreate an entity in the same Tx
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-6341?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas commented on AS7-6341:
-------------------------------------
I think that this log message should just be dropped down to debug
> EJB2 CMP - 'JBAS014172: Instance not found in cache' after remove and recreate an entity in the same Tx
> -------------------------------------------------------------------------------------------------------
>
> Key: AS7-6341
> URL: https://issues.jboss.org/browse/AS7-6341
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Priority: Minor
>
> If an entity is removed and new created within the same transaction the 'afterCompletition' procedure try to sync it twice.
> It looks like that the entity is registered twice in this case.
> The Exception is shown in the server.log, nevertheless the transactions and method execution will be succeed.
> The following Exception can be safely ignored.
> 08:17:10,005 ERROR [org.jboss.as.ejb3] (EJB default - 4) JBAS014138: Exception releasing entity: java.lang.IllegalStateException: JBAS014172: Instance [org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@31b489ae] not found in cache
> at org.jboss.as.ejb3.component.entity.entitycache.ReferenceCountingEntityCache.release(ReferenceCountingEntityCache.java:86) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.releaseInstance(EntityBeanSynchronizationInterceptor.java:154) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.access$200(EntityBeanSynchronizationInterceptor.java:56) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor$EntityBeanSynchronization.afterCompletion(EntityBeanSynchronizationInterceptor.java:219) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:402)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:103)
> at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
> at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:91) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:252) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:65) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:321) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:69) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:202) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months