October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3942) Investigate: race condition with clean shutdown and mod_cluster session draining

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3942?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3942: --------------------------------- Affects Version/s: 8.1.0.Final 8.0.0.Final > Investigate: race condition with clean shutdown and mod_cluster session draining > -------------------------------------------------------------------------------- > > Key: WFLY-3942 > URL: https://issues.jboss.org/browse/WFLY-3942 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.Beta1 > > > Probably same issue exists in WF as well, I will revalidate the logic for race conditions. > https://issues.jboss.org/browse/MODCLUSTER-399 > https://bugzilla.redhat.com/show_bug.cgi?id=1083563 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3942) Race condition with clean shutdown and mod_cluster session draining

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3942?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3942: --------------------------------- Summary: Race condition with clean shutdown and mod_cluster session draining (was: Investigate: race condition with clean shutdown and mod_cluster session draining) > Race condition with clean shutdown and mod_cluster session draining > ------------------------------------------------------------------- > > Key: WFLY-3942 > URL: https://issues.jboss.org/browse/WFLY-3942 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.Beta1 > > > Probably same issue exists in WF as well, I will revalidate the logic for race conditions. > https://issues.jboss.org/browse/MODCLUSTER-399 > https://bugzilla.redhat.com/show_bug.cgi?id=1083563 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-156) Defer the WFLY-184 validation until service start

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-156?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-156: ------------------------------------------------ Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1149612|https://bugzilla.redhat.com/show_bug.cgi?id=1149612] from ASSIGNED to POST > Defer the WFLY-184 validation until service start > ------------------------------------------------- > > Key: WFCORE-156 > URL: https://issues.jboss.org/browse/WFCORE-156 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > The WFLY-184 fix rejects the combination of any-ipv6-address and java.net.preferIPv4Stack=true in Stage.RUNTIME, but does so during service installation rather than in service start. The effect of this is failures occur even if the interface resource isn't being used; e.g. on a host controller. > This also leads to inconsistent behavior between "add" and "write-attribute", as the write-attribute handler doesn't install the service, and thus doesn't fail. It just sets reload-required. > Fix is to move the check into NetworkInterfaceService.start() and to make those services ON_DEMAND so the check won't occur until the interface is actually needed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3872) Recurring failure of EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-3872?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-3872: --------------------------------------- Another error that I noticed when the test here (or the similar encryptedAndSignedRequestFromAlice) fails is the following: {noformat} 2014-10-09 03:53:44,485 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-32) Interceptor for {http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy}EJBEncryptSecurityService#{http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy}sayHello has thrown exception, unwinding now: java.lang.NullPointerException at io.undertow.servlet.spec.ServletContextImpl.getResource(ServletContextImpl.java:237) at org.apache.cxf.transport.servlet.ServletContextResourceResolver.resolve(ServletContextResourceResolver.java:98) at org.apache.cxf.resource.DefaultResourceManager.findResource(DefaultResourceManager.java:113) at org.apache.cxf.resource.DefaultResourceManager.resolveResource(DefaultResourceManager.java:58) at org.apache.cxf.ws.security.wss4j.policyhandlers.AbstractBindingBuilder.getCrypto(AbstractBindingBuilder.java:1433) at org.apache.cxf.ws.security.wss4j.policyhandlers.AbstractBindingBuilder.getSignatureCrypto(AbstractBindingBuilder.java:1379) at org.apache.cxf.ws.security.wss4j.policyhandlers.AbstractBindingBuilder.getSignatureBuilder(AbstractBindingBuilder.java:1725) at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doSignature(AsymmetricBindingHandler.java:663) at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doEncryptBeforeSign(AsymmetricBindingHandler.java:359) at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.handleBinding(AsymmetricBindingHandler.java:105) at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:184) at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:99) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307) at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:83) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:243) at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:110) at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:131) at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136) at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-3.0.0.Beta1.jar:3.0.0.Beta1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:63) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:247) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:166) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:198) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:744) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] {noformat} In any case, I believe there must be something at lower level then WS causing these failures. > Recurring failure of EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn > -------------------------------------------------------------------------------------------- > > Key: WFLY-3872 > URL: https://issues.jboss.org/browse/WFLY-3872 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Alpha1 > Reporter: Brian Stansberry > Assignee: Alessio Soldano > > Since https://github.com/wildfly/wildfly/pull/6660 was submitted, EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn is failing regularly. Not every time but very often. > Alessio, you mentioned seeing some error logging from XAResourceRecoveryImpl, but that's in the logs on successful runs as well, and occurs prior to the test as well. That's a period background task from the transaction manager trying to perform recovery of some previous transaction. I don't see why it would have any impact on this test. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-156) Defer the WFLY-184 validation until service start

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-156?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-156: ----------------------------------------- Turns out the fact these interface services aren't ON_DEMAND was a bug in the WFCORE-102 patch. The patch removed that setting. > Defer the WFLY-184 validation until service start > ------------------------------------------------- > > Key: WFCORE-156 > URL: https://issues.jboss.org/browse/WFCORE-156 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > The WFLY-184 fix rejects the combination of any-ipv6-address and java.net.preferIPv4Stack=true in Stage.RUNTIME, but does so during service installation rather than in service start. The effect of this is failures occur even if the interface resource isn't being used; e.g. on a host controller. > This also leads to inconsistent behavior between "add" and "write-attribute", as the write-attribute handler doesn't install the service, and thus doesn't fail. It just sets reload-required. > Fix is to move the check into NetworkInterfaceService.start() and to make those services ON_DEMAND so the check won't occur until the interface is actually needed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1215) Only use XidWrapper if needed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1215?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1215: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1147881|https://bugzilla.redhat.com/show_bug.cgi?id=1147881] from POST to MODIFIED > Only use XidWrapper if needed > ----------------------------- > > Key: JBJCA-1215 > URL: https://issues.jboss.org/browse/JBJCA-1215 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final, 1.1.8.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1213) XA_RBEND should be included in check

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1213?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1213: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1147881|https://bugzilla.redhat.com/show_bug.cgi?id=1147881] from POST to MODIFIED > XA_RBEND should be included in check > ------------------------------------ > > Key: JBJCA-1213 > URL: https://issues.jboss.org/browse/JBJCA-1213 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final, 1.1.8.Final, 1.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1332) Integrate the compressed message support that was introduced in EJB client library

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1332?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1332: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1149023|https://bugzilla.redhat.com/show_bug.cgi?id=1149023] from POST to MODIFIED > Integrate the compressed message support that was introduced in EJB client library > ---------------------------------------------------------------------------------- > > Key: WFLY-1332 > URL: https://issues.jboss.org/browse/WFLY-1332 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha2 > > > https://issues.jboss.org/browse/EJBCLIENT-76 introduced a feature where the message stream that contains the EJB protocol message can be compressed. This involves a new message header which the server needs to support for the compression to be functional. This JIRA tracks the server side additions to support this feature. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3832) Upgrade JBMETA to 8.0.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3832?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3832: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1139640|https://bugzilla.redhat.com/show_bug.cgi?id=1139640] from POST to MODIFIED > Upgrade JBMETA to 8.0.1.Final > ----------------------------- > > Key: WFLY-3832 > URL: https://issues.jboss.org/browse/WFLY-3832 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-794) javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-794?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-794: ---------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1140755|https://bugzilla.redhat.com/show_bug.cgi?id=1140755] from POST to MODIFIED > javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi thrown when creating MBeanServerConnection > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-794 > URL: https://issues.jboss.org/browse/WFLY-794 > Project: WildFly > Issue Type: Bug > Components: JMX > Reporter: Alex Corvino > Assignee: Eduardo Martins > Labels: investigation_required > Fix For: 9.0.0.Alpha1 > > Attachments: jmx-test.jar, JmxClient.java, JMXConnectionBean.java, JmxServer.java > > > When trying to create a MBeanServerConnection to a NON-JBoss application from within an EJB a "javax.naming.NameNotFoundException" is thrown. > Steps to reproduce: > Set up a stand-alone application that exposes an MBean. (ActiveMQ will work in this case.) > Modify the attached JMXConnectionBean.java to connect to the ActiveMQ instance. > Deploy the bean. A NameNotFoundException will be thrown. > I've seen this behavior in 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final). > Note that this behavior is NOT seen when connecting to another JBoss server. > Full stack trace: > {code} > Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:340) [:1.6.0_26] > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) [:1.6.0_26] > at com.example.JMXConnectionBean.init(JMXConnectionBean.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] > at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:70) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ee.component.ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:44) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor$CustomSessionInvocationContext.proceed(SessionInvocationContextInterceptor.java:126) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:211) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:313) > at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56) > at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:42) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor.processInvocation(SessionInvocationContextInterceptor.java:71) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:152) > ... 9 more > Caused by: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:209) > at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_26] > at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1888) [:1.6.0_26] > at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1858) [:1.6.0_26] > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257) [:1.6.0_26] > ... 37 more > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2014