July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1403) Excluded/Banned transitive dependencies for Maven Dependency Resolver are too strict

by Karel Piwko (JIRA)

Excluded/Banned transitive dependencies for Maven Dependency Resolver are too strict ------------------------------------------------------------------------------------ Key: AS7-1403 URL: https://issues.jboss.org/browse/AS7-1403 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.0.0.Final Reporter: Karel Piwko Assignee: Paul Gier During 7.0.0.CR1 build, there was a decision to remove transitive dependencies from other projects and exclude/ban them in jboss-as-parent. This decision has effectively crippled usage of Maven Dependency Resolver, which wasn't used in CR1-date based testsuite, so the change passed silently. If user wants to use the ShrinkWrap Dependency Resolver in the AS7 testsuite, he won't get the required transitive dependencies, such as wagon or aether, so the resolver is unusable. According to disscussion with Vladimir, it would help "to flatten" dependency tree for ShrinkWrap dependency Resolver, however, that's only the part of the solution, the restrictions posed in AS7 parent must be relaxed afterwards. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

6
10
0 / 0

[JBoss JIRA] Created: (JBAS-8850) Transactional CDI events not work in case of remote EJB call

by Eugene Romanenko (JIRA)

Transactional CDI events not work in case of remote EJB call ------------------------------------------------------------ Key: JBAS-8850 URL: https://issues.jboss.org/browse/JBAS-8850 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.Final Reporter: Eugene Romanenko Assignee: Marius Bogoevici When EJB fires CDI event, observer method called only if TransactionPhase set to IN_PROGRESS. When TransactionPhase set to any other value (transactional event), JBoss shows error: {code}20:55:40,700 ERROR [org.jboss.weld.Event] WELD-000401 Failure while notifying an observer of event er.t2.TestEvent@78a17a{code} Looks like there problem with cdi events during remote call. Testcase: {code:title=TestEvent.java|borderStyle=solid} public class TestEvent { private String message; public TestEvent(String message) { this.message = message; } public String getMessage() { return message; } } {code} {code:title=T2Remote.java|borderStyle=solid} @Remote public interface T2Remote { void theTest(); } {code} {code:title=T2Bean.java|borderStyle=solid} @Stateless public class T2Bean implements T2Remote { @Inject private Event<TestEvent> events; @Override public void theTest() { events.fire(new TestEvent("from bean " + System.currentTimeMillis())); } } {code} {code:title=TestListener.java|borderStyle=solid} @Stateless public class TestListener { public void listen( @Observes(during=AFTER_COMPLETION) TestEvent evt ) { System.out.println("Event: " + evt.getMessage()); } } {code} Simple remote client: {code:title=Main.java|borderStyle=solid} public class Main { public static void main(String[] args) throws Exception { Properties properties = new Properties(); properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); properties.put(Context.PROVIDER_URL, "localhost"); Context ctx = new InitialContext( properties ); Object ref = ctx.lookup( "T2Bean/remote" ); T2Remote t = (T2Remote)ref; t.theTest(); System.out.println( "theTest() called!" ); } } {code} In debug log we have following exception: {code} 2011-01-25 09:13:04,359 DEBUG [org.jboss.ejb3.stateless.StatelessContainer] (WorkerThread#0[127.0.0.1:3536]) Received dynamic invocation for method with hash: -4087570856943461660 2011-01-25 09:13:04,359 DEBUG [org.jboss.weld.Event] (WorkerThread#0[127.0.0.1:3536]) WELD-000400 Sending event er.tst.TestEvent@151e0c7 directly to observer [method] public er.tst.TestListener.listen(TestEvent) 2011-01-25 09:13:04,359 ERROR [org.jboss.weld.Event] (WorkerThread#0[127.0.0.1:3536]) WELD-000401 Failure while notifying an observer of event er.tst.TestEvent@151e0c7 2011-01-25 09:13:04,359 DEBUG [org.jboss.weld.Event] (WorkerThread#0[127.0.0.1:3536]) throwing: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308 Unable to resolve any beans for Types: [interface org.jboss.weld.context.ejb.EjbRequestContext]; Bindings: [@org.jboss.weld.context.unbound.Unbound()] at org.jboss.weld.manager.BeanManagerImpl.getBean(BeanManagerImpl.java:788) [:6.0.0.Final] at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:80) [:6.0.0.Final] at org.jboss.weld.event.DeferredEventNotification$RunInRequest.run(DeferredEventNotification.java:103) [:6.0.0.Final] at org.jboss.weld.event.DeferredEventNotification.run(DeferredEventNotification.java:64) [:6.0.0.Final] at org.jboss.weld.event.TransactionSynchronizedRunnable.afterCompletion(TransactionSynchronizedRunnable.java:62) [:6.0.0.Final] at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:117) [:6.0.0.Final] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:371) [:6.0.0.Final] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:104) [:6.0.0.Final] at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:159) [:6.0.0.Final] at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1158) [:6.0.0.Final] at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:119) [:6.0.0.Final] at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) [:6.0.0.Final] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:82) [:0.0.1] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:255) [:0.0.1] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.required(CMTTxInterceptor.java:349) [:0.0.1] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invoke(CMTTxInterceptor.java:209) [:0.0.1] at org.jboss.ejb3.tx2.aop.CMTTxInterceptorWrapper.invoke(CMTTxInterceptorWrapper.java:52) [:0.0.1] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) [:1.0.0.GA] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA] at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) [:1.0.3] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:182) [:1.7.17] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) [:1.7.17] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA] at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) [:1.7.17] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA] at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.7.17] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA] at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA] at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) [:1.7.17] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA] at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:392) [:1.7.17] at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:53) [:1.7.17] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) [jboss-aop.jar:2.2.1.GA] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) [:1.0.1.GA] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:898) [:6.0.0.Final] at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791) [:6.0.0.Final] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744) [:6.0.0.Final] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548) [:6.0.0.Final] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) [:6.0.0.Final] 2011-01-25 09:13:04,375 DEBUG [org.jboss.remoting.transport.socket.ServerThread] (WorkerThread#0[127.0.0.1:3536]) WorkerThread#0[127.0.0.1:3536] closed socketWrapper: ServerSocketWrapper[Socket[addr=/127.0.0.1,port=3536,localport=3873].15fe804] {code} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-825) Fix or remove @Ignore in ParseAndMarshalModelsTestCase

by Thomas Diesler (JIRA)

Fix or remove @Ignore in ParseAndMarshalModelsTestCase ------------------------------------------------------ Key: AS7-825 URL: https://issues.jboss.org/browse/AS7-825 Project: Application Server 7 Issue Type: Sub-task Reporter: Thomas Diesler Assignee: Darran Lofthouse -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (AS7-1177) JavaMail not available

by Juergen Zimmermann (JIRA)

JavaMail not available ---------------------- Key: AS7-1177 URL: https://issues.jboss.org/browse/AS7-1177 Project: Application Server 7 Issue Type: Bug Components: Modules Affects Versions: 7.0.0.CR1 Reporter: Juergen Zimmermann JavaMail cannot be used as it was in JBossAS 6 and earlier. 1) I tried as in JBoss 6: @Resource(mappedName = "java:Mail") private Session mailer; ... and got this logging info within the Arquillian tests: 11:12:08,454 INFO [org.jboss.as.server.controller] (pool-1-thread-48) Deployment of "test.ear.ear" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.\"test.ear\".test.KundenverwaltungListener.\"env/de.swe2.kundenverwaltung.service.KundenverwaltungListener/mailer\".jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.KundenverwaltungListener.8","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.Dao.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.KundenverwaltungListener.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.KundenverwaltungResourceImpl.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.ValidationService.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.Kundenverwaltung.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.Artikelverwaltung.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.FileStore.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.RolesService.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.BestellverwaltungResourceImpl.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.PasswordService.START","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".jndiDependencyService","jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.Bestellverwaltung.START"]} 11:12:08,468 INFO [org.jboss.jpa] (MSC service thread 1-1) stopping Persistence Unit Service 'test.ear.ear/test.jar#swe2Persistence' 11:12:08,470 INFO [org.jboss.weld] (MSC service thread 1-1) Stopping weld service 2) I tried @Resource private Session mailer; ... and got this logging info within the Arquillian tests: 11:09:20,085 INFO [org.jboss.as.server.controller] (pool-1-thread-46) Deployment of "test.ear.ear" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"test.ear.ear\".\"test.jar\".component.KundenverwaltungListener.START"]} 11:09:20,094 INFO [org.jboss.jpa] (MSC service thread 1-2) stopping Persistence Unit Service 'test.ear.ear/test.jar#swe2Persistence' 11:09:20,098 INFO [org.jboss.weld] (MSC service thread 1-2) Stopping weld service -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
26
0 / 0

[JBoss JIRA] Created: (JBAS-8429) Verify log messages from OSGi bundles feed to aggreaged logfile

by Thomas Diesler (JIRA)

Verify log messages from OSGi bundles feed to aggreaged logfile --------------------------------------------------------------- Key: JBAS-8429 URL: https://jira.jboss.org/browse/JBAS-8429 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.0.0.M1 A bundle may use LogService, SLF4J, JDK, Apache Commons or JBoss Logging. All of these must feed to the common log system -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (AS7-850) Dependency on old JCA SPI

by Jesper Pedersen (JIRA)

Dependency on old JCA SPI ------------------------- Key: AS7-850 URL: https://issues.jboss.org/browse/AS7-850 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.0.Beta3 Reporter: Jesper Pedersen Assignee: jaikiran pai Priority: Blocker Fix For: 7.0.0.CR1 The EJB3 code still depend on the old JCA SPI. Remove jboss-jca-spi from the environment and port the classes to ironjacamar-core-spi. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-918) Distribution AS7 contains hidden temporary files from editing

by Marek Novotny (JIRA)

Distribution AS7 contains hidden temporary files from editing ------------------------------------------------------------- Key: AS7-918 URL: https://issues.jboss.org/browse/AS7-918 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Marek Novotny Priority: Minor There are jboss-7.0.0.Beta3/standalone/configuration/.standalone.xml.swo and jboss-7.0.0.Beta3/standalone/configuration/.standalone.xml.swp files from editing the standalone.xml. Distribution shouldn't distribute them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (AS7-999) Move tests from testsuite/integration (legacy) to api/spec/internals

by Andrew Rubinger (JIRA)

Move tests from testsuite/integration (legacy) to api/spec/internals -------------------------------------------------------------------- Key: AS7-999 URL: https://issues.jboss.org/browse/AS7-999 Project: Application Server 7 Issue Type: Task Components: Test Suite Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: 7.0.0.CR1 Parent task for moving tests from the unified legacy location to rely on the proper dependencies only: api/spec/internals -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (AS7-1368) Provide advanced datasource configuration options through the web interface

by Heiko Braun (JIRA)

Provide advanced datasource configuration options through the web interface --------------------------------------------------------------------------- Key: AS7-1368 URL: https://issues.jboss.org/browse/AS7-1368 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3044) Need BRMS-586/590 hotfix for Drools 5.1.1 / Salience firing order reversed or not observed on multple fact inserts post index

by Armand Welsh (JIRA)

Need BRMS-586/590 hotfix for Drools 5.1.1 / Salience firing order reversed or not observed on multple fact inserts post index ----------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3044 URL: https://issues.jboss.org/browse/JBRULES-3044 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.1.1.FINAL Environment: Windows 7/64, ReHat Enterprise Linux 6, Drools 5.1.1 running Java 6 JRE/SDK (all versions currently available from Oracle), 2 GB RAM, 20+ GB Free HD Space Reporter: Armand Welsh Assignee: Mark Proctor Priority: Critical Fix For: 5.1.1.FINAL When executing fireAllRules, all pre-index rules fire adhering to the salience prioritization. If, however, during post-index execution, facts are inserted that are used in the conditions of lower salience rules in the same activation group, the rule will fire, regardless of the fact a higher salience rule has already fired. This is further complicated when defining default rules of default salience (though any salience value will suffice so long as the default rule has the lowest salience within the activation group). When no pre-indexed facts are availble for the activation group, the default rule fires. along, with other activation group rules. During execution, a new fact is inserted that provides a hit for a higher salience rule in the same activation group as the default rule which already fired, however, the rule is not fired. In effect, pre-indexed facts are processed in descending salience order. whereas post-indexed facts are processed in ascending salience order. In all scenarios described, there is not a fire once restriction assigned. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011