July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1730) Wrong TCCL during ValidatorFactory retrieval

by Jozef Hartinger (JIRA)

Jozef Hartinger created WFLY-1730: ------------------------------------- Summary: Wrong TCCL during ValidatorFactory retrieval Key: WFLY-1730 URL: https://issues.jboss.org/browse/WFLY-1730 Project: WildFly Issue Type: Bug Affects Versions: 8.0.0.Alpha3 Reporter: Jozef Hartinger Fix For: 8.0.0.Beta1 Here https://github.com/wildfly/wildfly/blob/master/ee/src/main/java/org/jboss... the TCCL is set to the classloader of the ValidatorFactory. If the ValidatorFactory is LazyValidatorFactory which delegates to a client proxy obtained from Weld, this call fails with {noformat} Caused by: java.lang.IllegalStateException: JBAS016071: Singleton not set for ModuleClassLoader for Module "org.jboss.as.ee:main" from local module loader @76724357 (finder: local module finder @47a34181 (r$ at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:75) [wildfly-weld-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT] at org.jboss.weld.Container.instance(Container.java:54) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15] at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:70) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15] at org.jboss.weld.proxies.ValidatorFactory$618047133$Proxy$_$$_WeldClientProxy.getValidator(Unknown Source) [weld-core-impl-2.0.2.Final.jar:] at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.getValidator(LazyValidatorFactory.java:83) at org.jboss.as.ee.beanvalidation.ValidatorJndiInjectable.getInstanceSafely(ValidatorJndiInjectable.java:53) at org.jboss.as.ee.beanvalidation.ValidatorJndiInjectable.getInstanceClassName(ValidatorJndiInjectable.java:61) at org.jboss.as.naming.ServiceBasedNamingStore.list(ServiceBasedNamingStore.java:176) at org.jboss.as.naming.NamingContext.list(NamingContext.java:323) at org.jboss.as.naming.InitialContext.list(InitialContext.java:140) at org.jboss.as.naming.NamingContext.list(NamingContext.java:339) at javax.naming.InitialContext.list(InitialContext.java:455) [rt.jar:1.7.0_25] at org.jboss.as.test.integration.web.injection.SimpleServlet.testAS7_5347(SimpleServlet.java:59) [classes:] ... 29 more {noformat} My assumption is that setting the TCCL is not necessary here at all though I may be wrong. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-28) ejb timer service creates empty directories for all ejbs including those without timers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-28?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-28: --------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 910193|https://bugzilla.redhat.com/show_bug.cgi?id=910193] from ON_QA to VERIFIED > ejb timer service creates empty directories for all ejbs including those without timers > --------------------------------------------------------------------------------------- > > Key: WFLY-28 > URL: https://issues.jboss.org/browse/WFLY-28 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Priority: Minor > Labels: directory, ejb, timer > Fix For: 8.0.0.Alpha1 > > > ejb timer service creates empty directories for all ejbs include those without timers > Empty directories are being created for all ejbs, even those that do not use timers. > $JBOSS_HOME/.../data/timer-service-data/ -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-28) ejb timer service creates empty directories for all ejbs including those without timers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-28?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-28: --------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug 910193|https://bugzilla.redhat.com/show_bug.cgi?id=910193] Verified in EAP 6.1.1.ER3 > ejb timer service creates empty directories for all ejbs including those without timers > --------------------------------------------------------------------------------------- > > Key: WFLY-28 > URL: https://issues.jboss.org/browse/WFLY-28 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Priority: Minor > Labels: directory, ejb, timer > Fix For: 8.0.0.Alpha1 > > > ejb timer service creates empty directories for all ejbs include those without timers > Empty directories are being created for all ejbs, even those that do not use timers. > $JBOSS_HOME/.../data/timer-service-data/ -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-52) Locally transmitted context data is not received

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-52?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-52: --------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 909804|https://bugzilla.redhat.com/show_bug.cgi?id=909804] from ON_QA to VERIFIED > Locally transmitted context data is not received > ------------------------------------------------ > > Key: WFLY-52 > URL: https://issues.jboss.org/browse/WFLY-52 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wouter De Borger > Assignee: jaikiran pai > Labels: ejb > Fix For: 8.0.0.Alpha1 > > > 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-52) Locally transmitted context data is not received

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-52?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-52: --------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug 909804|https://bugzilla.redhat.com/show_bug.cgi?id=909804] verified in EAP 6.1.1.ER3 > Locally transmitted context data is not received > ------------------------------------------------ > > Key: WFLY-52 > URL: https://issues.jboss.org/browse/WFLY-52 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wouter De Borger > Assignee: jaikiran pai > Labels: ejb > Fix For: 8.0.0.Alpha1 > > > 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1406) Hibernate cannot process package-info.java any more

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-1406?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann commented on WFLY-1406: ------------------------------------------ Scott, I just built the latest sources for Alpha4 from Github. The issue is still there. However, I've no idea how to set a breakpoint inside WildFly. I looked at https://community.jboss.org/wiki/HackingOnWildFly , but could find anything. Could you give me some assistence, please? > Hibernate cannot process package-info.java any more > --------------------------------------------------- > > Key: WFLY-1406 > URL: https://issues.jboss.org/browse/WFLY-1406 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha2 > Reporter: Juergen Zimmermann > Attachments: javap.log, server.log, server.log.zip, shop2.war, tar.log > > > I tried the snapshot which contains Hibernate 4.3.0.Beta2. However, package-info.java files are causing problems. For instance, the package de.shop.artikelverwaltung.domain has a package-info.java which causes a NoClassDefFoundError: > "IllegalName: de/shop/artikelverwaltung/domain.package-info". Please see the stacktrace below. > Here is an example for package-info.java which was working with WildFly 8.0.0.Alpha1: > @XmlAccessorType(FIELD) > @Vetoed > package de.shop.artikelverwaltung.domain; > import static javax.xml.bind.annotation.XmlAccessType.FIELD; > import javax.enterprise.inject.Vetoed; > import javax.xml.bind.annotation.XmlAccessorType; > The stacktrace: > ... > 09:29:53,880 WARN [org.jboss.modules] Failed to define class de/shop/artikelverwaltung/domain.package-info in Module "deployment.shop2.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link de/shop/artikelverwaltung/domain/package-info (Module "deployment.shop2.war:main" from Service Module Loader) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.findClass(ClassLoaderServiceImpl.java:218) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at java.lang.ClassLoader.loadClass(ClassLoader.java:423) [rt.jar:1.7.0_21] > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) [rt.jar:1.7.0_21] > at org.hibernate.annotations.common.util.ReflectHelper.classForName(ReflectHelper.java:160) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final] > at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.packageForName(JavaReflectionManager.java:121) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final] > at org.hibernate.cfg.AnnotationBinder.bindPackage(AnnotationBinder.java:262) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.cfg.Configuration.addPackage(Configuration.java:792) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.buildHibernateConfiguration(EntityManagerFactoryBuilderImpl.java:1174) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:839) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:213) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:58) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:107) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] > Caused by: java.lang.NoClassDefFoundError: IllegalName: de/shop/artikelverwaltung/domain.package-info > at java.lang.ClassLoader.preDefineClass(ClassLoader.java:646) [rt.jar:1.7.0_21] > at java.lang.ClassLoader.defineClass(ClassLoader.java:785) [rt.jar:1.7.0_21] > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final] > ... 28 more -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1541) UT005013 with RichFaces 5 and the tag <r:push> which uses WebSockets

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-1541?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann closed WFLY-1541. ------------------------------------ Fix Version/s: 8.0.0.Beta1 Resolution: Done > UT005013 with RichFaces 5 and the tag <r:push> which uses WebSockets > -------------------------------------------------------------------- > > Key: WFLY-1541 > URL: https://issues.jboss.org/browse/WFLY-1541 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.Alpha2 > Reporter: Juergen Zimmermann > Assignee: Stuart Douglas > Fix For: 8.0.0.Beta1 > > > I'm using a WildFly 8.0.0.Alpha2 snapshot with Undertow 1.0.0.Alpha19. The snapshot is configured for Mojarra 2.1.23 instead of 2.2.0 because of the new RichFaces 5.0.0.Alpha1 which still cannot use Mojarra 2.2. During a websocket push via <r:push> I'm getting the stacktrace below. RichFaces itself is using Atmosphere 1.0.13 for WebSockets. > Log messages when Atmosphere is started: > {code} > 09:38:56,670 INFO [org.atmosphere.cpr.AtmosphereFramework] Auto detecting atmosphere handlers /WEB-INF/classes/ > 09:38:56,702 INFO [org.atmosphere.cpr.AtmosphereFramework] Auto detecting WebSocketHandler in /WEB-INF/classes/ > 09:38:56,702 INFO [org.atmosphere.cpr.AtmosphereFramework] Installed WebSocketProtocol org.atmosphere.websocket.protocol.SimpleHttpProtocol > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] Atmosphere is using async support: org.atmosphere.container.BlockingIOCometSupport running under container: Undertow - 1.0.0.Alpha19 > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] Installed AtmosphereInterceptor Track Message Size Interceptor using |. > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] Installed Default AtmosphereInterceptor [Android Interceptor Support, SSE Interceptor Support, JSONP Interceptor Support, Atmosphere JavaScript Protocol, Browser disconnection detection, Track Message Size Interceptor using |]. Set org.atmosphere.cpr.AtmosphereInterceptor.disableDefaults in your xml to disable them. > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] Using BroadcasterCache: org.atmosphere.cache.HeaderBroadcasterCache > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] Shared ExecutorService supported: true > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] HttpSession supported: false > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] Using BroadcasterFactory: org.atmosphere.cpr.DefaultBroadcasterFactory > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] Using WebSocketProcessor: org.atmosphere.websocket.DefaultWebSocketProcessor > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] Using Broadcaster: org.atmosphere.cpr.DefaultBroadcaster > 09:38:56,718 INFO [org.atmosphere.cpr.AtmosphereFramework] Atmosphere Framework 1.0.13 started. > {code} > Stacktrace: > {code} > 09:40:44,640 ERROR [io.undertow.request.io] UT005013: An IOException occurred: java.io.IOException: Eine bestehende Verbindung wurde softwaregesteuert > durch den Hostcomputer abgebrochen > at sun.nio.ch.SocketDispatcher.write0(Native Method) [rt.jar:1.7.0_21] > at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:51) [rt.jar:1.7.0_21] > at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:94) [rt.jar:1.7.0_21] > at sun.nio.ch.IOUtil.write(IOUtil.java:65) [rt.jar:1.7.0_21] > at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:450) [rt.jar:1.7.0_21] > at org.xnio.nio.NioSocketConduit.write(NioSocketConduit.java:148) [xnio-nio-3.1.0.CR3.jar:3.1.0.CR3] > at io.undertow.server.HttpResponseConduit.write(HttpResponseConduit.java:476) > at io.undertow.conduits.ChunkedStreamSinkConduit.flush(ChunkedStreamSinkConduit.java:184) > at org.xnio.conduits.ConduitStreamSinkChannel.flush(ConduitStreamSinkChannel.java:147) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3] > at io.undertow.server.HttpServerExchange$WriteDispatchChannel.flush(HttpServerExchange.java:1500) > at io.undertow.server.HttpServerExchange.closeAndFlushResponse(HttpServerExchange.java:1298) > at io.undertow.server.HttpServerExchange.endExchange(HttpServerExchange.java:1287) > at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:47) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:607) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > {code} -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1729) Provide an access control user guide chapter

by Heiko Braun (JIRA)

Heiko Braun created WFLY-1729: --------------------------------- Summary: Provide an access control user guide chapter Key: WFLY-1729 URL: https://issues.jboss.org/browse/WFLY-1729 Project: WildFly Issue Type: Task Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1322) Cannot set up serverBindAddress for secondarySocket in bisocket transport

by Igor Kostromin (JIRA)

[ https://issues.jboss.org/browse/JBREM-1322?page=com.atlassian.jira.plugin... ] Igor Kostromin commented on JBREM-1322: --------------------------------------- My mistake - the option allows set IP address will be useless here, it should be setting like "Ignore received secondary address, use address from original URI". > Cannot set up serverBindAddress for secondarySocket in bisocket transport > ------------------------------------------------------------------------- > > Key: JBREM-1322 > URL: https://issues.jboss.org/browse/JBREM-1322 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: transport > Affects Versions: 2.5.4.SP4 > Reporter: Igor Kostromin > Assignee: Ron Sigal > Fix For: 2.5.4.SP5 > > > Using IS_CALLBACK_SERVER = true. > In BisocketClientInvoker.java:355 > InvokerLocator getSecondaryLocator() throws Throwable { > ... > 355: Object o = invoke(r); > ... > } > It retrieves host from server, but if you want to use original client invoker host, you cannot do this (it is necessary if server is behind translating firewall). If you want to do this, you have to patch this code manually to > Object o = invoke(r); > // DZ: patch to use original server address for creating secondary connection > // instead of address retrieved from server (because server will return jboss bind address > // that can be local address, inaccessible from client) > InvokerLocator patchedLocator = new InvokerLocator( (( InvokerLocator ) o).getOriginalURI().replace( > (( InvokerLocator ) o).getHost(), this.getLocator().getHost() ) > ); > log.debug("secondary locator: " + o); > log.debug("patched secondary locator: " + patchedLocator); > return patchedLocator; > and rebuild jboss-remoting project. > For ports there are settings SECONDARY_BIND_PORT, SECONDARY_CONNECT_PORT allowing to set up them as you want. For address there is no one to do this. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1728) Web Console: Role specific entry points

by Heiko Braun (JIRA)

Heiko Braun created WFLY-1728: --------------------------------- Summary: Web Console: Role specific entry points Key: WFLY-1728 URL: https://issues.jboss.org/browse/WFLY-1728 Project: WildFly Issue Type: Feature Request Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun some roles (i.e. deployer, auditer) can benefit from specific entry points -- 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

12 years, 9 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 July 2013