July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1005) TxPropagationInterceptor requires use of IsLocalInterceptor

by Brian Stansberry (JIRA)

TxPropagationInterceptor requires use of IsLocalInterceptor ----------------------------------------------------------- Key: EJBTHREE-1005 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1005 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor The TxPropagationInterceptor will fail if a tx is running and a call to a local bean is not routed through IsLocalInterceptor.invokeLocal(). This means the IsLocalInterceptor.invokeLocal() routing can't be effectively disabled, which is a user request that comes up fairly often for EJB2. Users request this when they want the EJB requests load balanced, with no preference for the in-VM bean. The same thing isn't a problem in EJB2, where transaction propagation is a function of the Invoker; the LocalInvoker just doesn't do it. But EJB3 doesn't have that option -- Remoting will bypass any invoker if it detects an in-VM target. Couple possibilities: 1) Change TxPropagationInterceptor from: Transaction tx = tm.getTransaction(); if (tx != null) throw new RuntimeException("cannot import a transaction context when a transaction is already associated with the thread"); Transaction importedTx = TransactionPropagationContextUtil.getTPCImporter().importTransactionPropagationContext(tpc); tm.resume(importedTx); to: Transaction tx = tm.getTransaction(); Transaction importedTx = TransactionPropagationContextUtil.getTPCImporter().importTransactionPropagationContext(tpc); if (tx != null) { if (tx != importedTx) { throw new RuntimeException("cannot import a transaction context when a transaction is already associated with the thread"); } else { tm.resume(importedTx); } 2) Have IsLocalInterceptor add some transient metadata to the invocation if it doesn't route the request via invokeLocal() -- i.e. if it expects the call is going remote. TxPropagationInterceptor can check for that metadata; if found it knows the call didn't actually go remote and can skip the import of the tx. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-862) EJB 3.0 dependencies injection accross EARs

by Roland R?z (JIRA)

EJB 3.0 dependencies injection accross EARs ------------------------------------------- Key: EJBTHREE-862 URL: http://jira.jboss.com/jira/browse/EJBTHREE-862 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: Windows, JDK 1.5.0_06-b05, JBoss 4.0.5 GA, EJB-3.0_RC9 Patch 1 Reporter: Roland R?z We have a deployment schema similar to the example from EJB 3.0 specification (chapter 19.6 Example): ear1: FirstReferencer.jar Class-Path:FirstReferencer-client.jar SecondReferencer-client.jar FirstReferencer-client.jar SecondReferencer-client.jar ear2: SecondReferencer.jar Class-Path:SecondReferencer-client.jar SecondReferencer-client.jar deployment descriptor contains: <ejb-client-jar>SecondReferencer-client.jar</ejb-client-jar> There are two session beans FirstReferencer and SecondReferencer. FirstReferencer references SecondReferencer over the dependency injection. After deployment if we call the business method on the FirstReferencer, which in turn calls SecondReferencer we get exception like this: 16:22:12,155 ERROR [STDERR] java.lang.RuntimeException: Non matching type for inject of field: SecondReferencer FirstReferencerEjb.secondReferencer for type: $Proxy79 of jndiName env/FirstReferencerEjb/secondReferencer intfs: , SecondReferencer, org.jboss.ejb3.JBossProxy, javax.ejb.EJBObject 16:22:12,155 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:135) 16:22:12,155 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:104) 16:22:12,155 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:61) 16:22:12,155 ERROR [STDERR] at org.jboss.ejb3.AbstractPool.create(AbstractPool.java:92) 16:22:12,155 ERROR [STDERR] at org.jboss.ejb3.ThreadlocalPool.get(ThreadlocalPool.java:48) 16:22:12,165 ERROR [STDERR] at org.jboss.ejb3.cache.simple.SimpleStatefulCache.create(SimpleStatefulCache.java:209) 16:22:12,165 ERROR [STDERR] at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:303) 16:22:12,165 ERROR [STDERR] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) 16:22:12,165 ERROR [STDERR] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) 16:22:12,185 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException 16:22:12,185 ERROR [STDERR] at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63) 16:22:12,185 ERROR [STDERR] at java.lang.reflect.Field.set(Field.java:656) 16:22:12,185 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:119) 16:22:12,185 ERROR [STDERR] ... 13 more On debuging and from the stacktrace of the exception we can see that the lookup for refernced EJB works fine but the assigning over reflaction fails. It seems to be a ClassLoading issue 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

16 years, 2 months

7
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-942) Performance comparisons between MINA and JBR

by Tim Fox (JIRA)

Performance comparisons between MINA and JBR -------------------------------------------- Key: JBMESSAGING-942 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-942 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: Miscellaneous Perform performance coparisons between Apache MINA and JBoss 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

16 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBRULES-497) Joda datetime API integration

by Michael Neale (JIRA)

Joda datetime API integration ----------------------------- Key: JBRULES-497 URL: http://jira.jboss.com/jira/browse/JBRULES-497 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Michael Neale Assigned To: Mark Proctor http://joda-time.sourceforge.net/userguide.html Would be VERY nice to have this working at the parser level to parser dates in a string, but also possibly in our expression language to overload "+", "-" etc for subtracting dates/fragments of dates: eg: today - "6Months" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-753) Similar to JBC/JGroups, add an ant-dist folder and build.bat/build.sh

by Galder Zamarreno (JIRA)

Similar to JBC/JGroups, add an ant-dist folder and build.bat/build.sh --------------------------------------------------------------------- Key: JBMESSAGING-753 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-753 Project: JBoss Messaging Issue Type: Feature Request Components: Build System Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor Fix For: 1.2.1 Add to source and make messaging add it to the binary distribution under util directory. That should speed up patching AS for customers and would guarantee that they use the Ant version that we want them to use. This is currently implemented in JBC and JGroups and I find it very useful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

6
13
0 / 0

[JBoss JIRA] Created: (BPEL-244) Support for BPEL process instance monitoring in jBPM admin console

by Meghana Joglekar (JIRA)

Support for BPEL process instance monitoring in jBPM admin console ------------------------------------------------------------------ Key: BPEL-244 URL: http://jira.jboss.com/jira/browse/BPEL-244 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Reporter: Meghana Joglekar Assigned To: Alejandro Guizar One can currently run BPEL processes on jBPM engine and check the log files to see the runtime report. But this process is not efficient in monitoring how the process is doing, what processes are running, what went wrong when a fault occurred etc. It will be nice to have administration console to see this information. The administration console can then list the process instances that are running, show visual graph of the instance and for each node in the graph more information about it. ActiveBPEL and OracleBPEL both provide such consoles and they are great tools for administrators. It will be nice if it also provides 'delete' functionality for stalled processes or old processes. The list could go on but in its basic form, processes listing, process instance listing and then more information about them [instances] will be useful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-759) CLONE -Unable to add package after it was added and removed

by Brugger Antony (JIRA)

CLONE -Unable to add package after it was added and removed ----------------------------------------------------------- Key: JBRULES-759 URL: http://jira.jboss.com/jira/browse/JBRULES-759 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.0.4 Environment: Windows2000 Advanced Server JBRules3.0.4 Reporter: Brugger Antony Assigned To: Edson Tirelli Fix For: 3.0.5 Unable remove a rule package when it was added after it has been added and removed. I have seen the issue [#JBRULES-358]. My test go a little far than [#JBRULES-358]. I remove the package again when it was added for the seconn time, then an exception was thrown. My test case is: public void testRuleBaseRemove() throws Exception { RuleBase ruleBase = RuleBaseFactory.newRuleBase(); File file = new File("test.drl"); //add and remove PackageBuilder builder = new PackageBuilder(); builder.addPackageFromDrl(new FileReader(file)); Package pkg = builder.getPackage(); ruleBase.addPackage(pkg); ruleBase.removePackage(pkg.getName()); //add and remove again builder = new PackageBuilder(); builder.addPackageFromDrl(new FileReader(file)); pkg = builder.getPackage(); ruleBase.addPackage(pkg); ruleBase.removePackage(pkg.getName()); } the exception is throw: java.lang.NullPointerException at org.drools.reteoo.HashedObjectSinkList.remove(HashedObjectSinkList.java:102) at org.drools.reteoo.ObjectTypeNode.remove(ObjectTypeNode.java:245) at org.drools.reteoo.AlphaNode.remove(AlphaNode.java:211) at org.drools.reteoo.AlphaNode.remove(AlphaNode.java:211) at org.drools.reteoo.LeftInputAdapterNode.remove(LeftInputAdapterNode.java:285) at org.drools.reteoo.TerminalNode.remove(TerminalNode.java:297) at org.drools.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:589) at org.drools.reteoo.ReteooRuleBase.removeRule(ReteooRuleBase.java:244) at org.drools.common.AbstractRuleBase.removePackage(AbstractRuleBase.java:338) at com.zte.ums.uep.pal.fm.osf.rules.core.RuleBaseTest.testRuleBaseRemove(RuleBaseTest.java:71) 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 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) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-912) ejb-jar.xml injected EntityManger fails in @PostConstruct annotated methods

by Andrew Redhead (JIRA)

ejb-jar.xml injected EntityManger fails in @PostConstruct annotated methods --------------------------------------------------------------------------- Key: EJBTHREE-912 URL: http://jira.jboss.com/jira/browse/EJBTHREE-912 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: Identified on jboss-4.0.5.GA from jems installer 1.2.GA, still present in head from svn co http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_0/ as of 13th March 2007. Tests run agains JDK 1.5 on Win XP (sp2) Reporter: Andrew Redhead Using an ejb-jar.xml file to inject an EntityManger into an EJB3 stateless session bean succeeds for bean interface methods but fails for @PostConstruct methods. In both cases the reference to the EntityManager is non-null, however in the @PostConstruct method, accessing the EnityManger underlying delegate fails. The test cases provide both an "API" interface case (which passes) and an @PostConstruct case, which currently 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

16 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (GPD-74) Add a server adaptor to enable starting and stopping the 'jbpm server'.

by Koen Aers (JIRA)

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

16 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (GPD-37) include snap to grid

by Koen Aers (JIRA)

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

16 years, 3 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007