January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2945) Change the domain model paths system to not use services

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-2945?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-2945: ----------------------------- Fix Version/s: 7.2.0.Alpha1 (was: Open To Community) > Change the domain model paths system to not use services > -------------------------------------------------------- > > Key: AS7-2945 > URL: https://issues.jboss.org/browse/AS7-2945 > Project: Application Server 7 > Issue Type: Enhancement > Components: Domain Management > Reporter: David Lloyd > Assignee: Kabir Khan > Fix For: 7.2.0.Alpha1 > > > Using services for path references has two distinct disadvantages: > * It makes it difficult or impossible to detect changes (the only way to change a path is to restart the service) > * If a path consumer is not a service, it is difficult to use path values > What we should have instead is have a registration mechanism so that when a path is used, the reference is tracked in the model. This lets us detect backreferences in the event where a path is to be deleted. This would also enable us to send a notification when a path is changed, so that changing a path also causes an update or "refresh" on all referencing domain attributes. This way, for example, if I change the base path for the log directory, all the log handlers can automatically be updated as well as part of the same operation, using their existing update logic. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6143) HiloKeygenerator not registered in JNDI

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6143?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated AS7-6143: ----------------------------- Fix Version/s: 7.2.0.Alpha1 (was: Open To Community) > HiloKeygenerator not registered in JNDI > --------------------------------------- > > Key: AS7-6143 > URL: https://issues.jboss.org/browse/AS7-6143 > Project: Application Server 7 > Issue Type: Feature Request > Components: EJB > Affects Versions: 7.1.1.Final > Reporter: Manuel Fehlhammer > Assignee: Tomaz Cerar > Labels: cmp > Fix For: 7.2.0.Alpha1 > > > The HiLoKeygenerator from subsystem cmp is not registered in JNDI. > Therefore it is not really usable. > I managed to get the service successfully started up with the following subsystem confiuration in standalone.xml: > {code:xml} > <subsystem xmlns="urn:jboss:domain:cmp:1.0"> > <key-generators> > <hilo name="itemidgenerator"> > <block-size> > 10 > </block-size> > <data-source> > java:jboss/datasources/MySqlDS > </data-source> > <id-column> > highvalue > </id-column> > <sequence-column> > sequencename > </sequence-column> > <sequence-name> > itemid > </sequence-name> > <table-name> > HiLoSequences > </table-name> > </hilo> > </key-generators> > </subsystem> > {code} > > But I do not find any JNDI registration related to this HiLoKeygenerator. > From JBOSS 5.x times I know that the generator was bound as "KeyGeneratorFactory" or something. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6143) HiloKeygenerator not registered in JNDI

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6143?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned AS7-6143: -------------------------------- Assignee: Tomaz Cerar > HiloKeygenerator not registered in JNDI > --------------------------------------- > > Key: AS7-6143 > URL: https://issues.jboss.org/browse/AS7-6143 > Project: Application Server 7 > Issue Type: Feature Request > Components: EJB > Affects Versions: 7.1.1.Final > Reporter: Manuel Fehlhammer > Assignee: Tomaz Cerar > Labels: cmp > Fix For: Open To Community > > > The HiLoKeygenerator from subsystem cmp is not registered in JNDI. > Therefore it is not really usable. > I managed to get the service successfully started up with the following subsystem confiuration in standalone.xml: > {code:xml} > <subsystem xmlns="urn:jboss:domain:cmp:1.0"> > <key-generators> > <hilo name="itemidgenerator"> > <block-size> > 10 > </block-size> > <data-source> > java:jboss/datasources/MySqlDS > </data-source> > <id-column> > highvalue > </id-column> > <sequence-column> > sequencename > </sequence-column> > <sequence-name> > itemid > </sequence-name> > <table-name> > HiLoSequences > </table-name> > </hilo> > </key-generators> > </subsystem> > {code} > > But I do not find any JNDI registration related to this HiLoKeygenerator. > From JBOSS 5.x times I know that the generator was bound as "KeyGeneratorFactory" or something. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3693) Pull Request to update smooks to 1.5.1

by George Varsamis (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3693?page=com.atlassian.jira.plug... ] George Varsamis commented on JBRULES-3693: ------------------------------------------ Hi guys, Although I think this has been resolved, can you please verify and close the ticket if it is resolved. Thanks George. > Pull Request to update smooks to 1.5.1 > -------------------------------------- > > Key: JBRULES-3693 > URL: https://issues.jboss.org/browse/JBRULES-3693 > Project: JBRULES > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Alpha1 > Reporter: George Varsamis > Assignee: Mark Proctor > Fix For: 6.0.0.Alpha1 > > > Switchyard requires Smooks v 1.5.1 . I have updated drools parent to use smooks 1.5.1 and also updated the source code in droolsjbpm-integration/drools-pipeline to reflect this. The change is trivial. I have run the tests and the change had no adverse effect on the codebase. > I will attach the pull requests to this ticket. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6356) Locally transmitted context data is not received

by Wouter De Borger (JIRA)

[ https://issues.jboss.org/browse/AS7-6356?page=com.atlassian.jira.plugin.s... ] Wouter De Borger updated AS7-6356: ---------------------------------- Steps to Reproduce: from within a client-side ejb interceptor add some data with context.getContextData().put(...). On the server-side ejb interceptor try to read it with context.getContextData().get(...). Both EJB's should be on the same machine > Locally transmitted context data is not received > ------------------------------------------------ > > Key: AS7-6356 > URL: https://issues.jboss.org/browse/AS7-6356 > Project: Application Server 7 > Issue Type: Bug > Components: Remoting > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wouter De Borger > Assignee: David Lloyd > > ContextData attached to request is not transmitted when LocalEJBReceiver is used. > org.jboss.as.ejb3.remote.LocalEJBReceiver:177 > context.setContextData(new HashMap<String, Object>()); > see also https://issues.jboss.org/browse/AS7-5021 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6356) Locally transmitted context data is not received

by Wouter De Borger (JIRA)

[ https://issues.jboss.org/browse/AS7-6356?page=com.atlassian.jira.plugin.s... ] Wouter De Borger updated AS7-6356: ---------------------------------- Labels: ejb (was: ) > Locally transmitted context data is not received > ------------------------------------------------ > > Key: AS7-6356 > URL: https://issues.jboss.org/browse/AS7-6356 > Project: Application Server 7 > Issue Type: Bug > Components: Remoting > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wouter De Borger > Assignee: David Lloyd > Labels: ejb > > ContextData attached to request is not transmitted when LocalEJBReceiver is used. > org.jboss.as.ejb3.remote.LocalEJBReceiver:177 > context.setContextData(new HashMap<String, Object>()); > see also https://issues.jboss.org/browse/AS7-5021 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6365) Hibernate/Infinispan 2nd Level Caches set to transaction-mode=NONE stop functioning after an explicit eviction

by Fredrik Lagerblad (JIRA)

Fredrik Lagerblad created AS7-6365: -------------------------------------- Summary: Hibernate/Infinispan 2nd Level Caches set to transaction-mode=NONE stop functioning after an explicit eviction Key: AS7-6365 URL: https://issues.jboss.org/browse/AS7-6365 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Affects Versions: 7.1.3.Final (EAP) Reporter: Fredrik Lagerblad Assignee: Scott Marlow The caches in the 'infinispan' subsystem configured with <transaction mode="NONE"/> get stuck in state= CLEARING when you perform a programmatic evict() on them to clear the caches. (Using e.g. em.getEntityManagerFactory().getCache().evictAll() ) The problem seem to lie within the class 'org.hibernate.cache.infinispan.impl.BaseRegion, where the 'checkValid' method fails to clear the cache (and set back the state to VALID). The reason it fails is due to that it calls: cacheAdapter.withinTx() , which in turn tries to get the TransactionManager from the cache (which seems to be null for these non-transactional caches), and then NPEs on the tm.begin(); The NPE is caught and logs out "Could not invalidate region: null", and never set the state in VALID. So from thereon the caches are in an Invalid state and is not used anymore by Infinispan, thus leading to much performance. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-1535) More management operations for timers

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-1535?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-1535: ------------------------------------- It does not, but if you start working on this in a separate branch there is a good chance there will be a lot of conflicts. > More management operations for timers > ------------------------------------- > > Key: AS7-1535 > URL: https://issues.jboss.org/browse/AS7-1535 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management, EJB > Reporter: Stuart Douglas > Assignee: Bartosz Baranowski > Fix For: 7.3.0.Alpha1 > > > Using the management api it should be possible to perform additional operations on timers such as: > suspending > cancelling > invoking a timeout method -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-1535) More management operations for timers

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/AS7-1535?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski commented on AS7-1535: ----------------------------------------- Yeah, but at first glance this branch does not change mgmt API and timer service much. > More management operations for timers > ------------------------------------- > > Key: AS7-1535 > URL: https://issues.jboss.org/browse/AS7-1535 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management, EJB > Reporter: Stuart Douglas > Assignee: Bartosz Baranowski > Fix For: 7.3.0.Alpha1 > > > Using the management api it should be possible to perform additional operations on timers such as: > suspending > cancelling > invoking a timeout method -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6339) Unable to propagate security context using IIOP between two AS7 server instances

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6339?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6339. --------------------------------- Assignee: Stuart Douglas (was: Stefan Guilhen) Resolution: Done > Unable to propagate security context using IIOP between two AS7 server instances > -------------------------------------------------------------------------------- > > Key: AS7-6339 > URL: https://issues.jboss.org/browse/AS7-6339 > Project: Application Server 7 > Issue Type: Bug > Components: IIOP > Affects Versions: 7.1.3.Final (EAP) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 7.2.0.Alpha1 > > > Because AS7 uses the SASClientIdentityInterceptor it expects that the security context will be propagated using a trust based mechanism, however this trust based mechanism has not actually been fully implemented. > In EJBCorbaServant there is some code that comes from AS6 that just assumes username=password, with a comment that this needs to be removed once we have a mechanism to establish trust. > > For now I think that we need to do two things: > - Allow the server to easily use the SASClientInterceptor > - Use the SASCurrent as a credential in EjbCorbaServant, so a custom login module can be used to establish trust -- 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, 5 months

1
0
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 January 2013