[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ]
Kabir Khan reopened WFLY-8449:
------------------------------
Reverting https://github.com/wildfly/wildfly/pull/10173 as it causes problems elsewhere
> EJB contextData not sent back to client in response
> ---------------------------------------------------
>
> Key: WFLY-8449
> URL: https://issues.jboss.org/browse/WFLY-8449
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Fedor Gavrilov
> Assignee: Fedor Gavrilov
> Labels: downstream_dependency, ejb
> Fix For: 11.0.0.Beta1
>
>
> With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors.
> Since AS7 and WildFly the only possibility is to pass such context from the client to the server.
> It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations.
> This was used to return i.e. tracking or additional usefull informations.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-8946) The fix for WFLY-4625 breaks PolicyContext("javax.security.auth.subject.container") in CXF web service with STS
by Petr Jurak (JIRA)
Petr Jurak created WFLY-8946:
--------------------------------
Summary: The fix for WFLY-4625 breaks PolicyContext("javax.security.auth.subject.container") in CXF web service with STS
Key: WFLY-8946
URL: https://issues.jboss.org/browse/WFLY-8946
Project: WildFly
Issue Type: Bug
Components: EJB, Security, Web Services
Reporter: Petr Jurak
Assignee: Darran Lofthouse
Web service with STS (Picketlink) returns wrong subject with PolicyContext("javax.security.auth.subject.container").
It seems that configured login modules are not called since SecurityContext was created by SAML2Handler for the same security domain and are skipped because of WFLY-4625.
Reproducer is attached in BZ-1352418.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2970) Export a low MALLOC_ARENA_MAX value in standalone.conf and domain.conf
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created WFCORE-2970:
-----------------------------------------
Summary: Export a low MALLOC_ARENA_MAX value in standalone.conf and domain.conf
Key: WFCORE-2970
URL: https://issues.jboss.org/browse/WFCORE-2970
Project: WildFly Core
Issue Type: Enhancement
Components: Scripts
Reporter: Rostislav Svoboda
Assignee: Tomaz Cerar
This is a task that came out of research done by [~andy.miller] on WF/EAP memory use in cloud environments.
Our launch scripts for *nix environments should set MALLOC_ARENA_MAX, e.g.
{code}
export MALLOC_ARENA_MAX=${MALLOC_ARENA_MAX:-1}
{code}
See http://info.prelert.com/blog/java-8-and-virtual-memory-on-linux for background.
The default glibc settings of allowing up to 128 malloc arenas make very little sense for a java application, since the vm asks the os for a few large memory allocations and then manages those areas itself. Leaving that default setting in place will result in a very large virtual memory size for the VM. It's just virtual, not resident, memory, so controlling this to a large extent is just a matter of having a better image for people who don't understand the distinction. But as is mentioned in the linked blog post's discussion of mlockall() and Elasticsearch, there may be some more concrete implications as well.
The initial recommendation on this was to set the value to 1, but this bears some research/discussion. For example hadoop uses 4 (https://issues.apache.org/jira/browse/HADOOP-7154), and a bit of googling of "MALLOC_ARENA_MAX java" leads to some entries mentioning using 2 or 3.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JGRP-2172) Non-blocking flow control
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2172?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2172:
--------------------------------
[~rvansa] Good idea! Yes, I'm thinking UFC2/MFC2 makes sense, too. Using a queue makes this more generic and once UFC2 / MFC2 has proven its stability in the field, we can always deprecate UFC / MFC.
Thanks for the input,
> Non-blocking flow control
> -------------------------
>
> Key: JGRP-2172
> URL: https://issues.jboss.org/browse/JGRP-2172
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.4
>
>
> Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.
> Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded). The max queue size is given in bytes, so we can estimate what the memory penalty for reaching that size would be (if bounded).
> The queued messages are sent when credits arrive. TBD: when credits arrive, should blocked threads or queued messages be released first?
> Non-blocking flow control can be used by both external and internal threads.
> If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1610) Runtime Exception
by Salman Khan (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1610?page=com.atlassian.jira.plugi... ]
Salman Khan reopened DROOLS-1610:
---------------------------------
I can't find any issues with the dependencies and whatever you guys had suggested I'm using the same. Kindly consider.
Thanks
> Runtime Exception
> ------------------
>
> Key: DROOLS-1610
> URL: https://issues.jboss.org/browse/DROOLS-1610
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.Final
> Reporter: Salman Khan
> Assignee: Mario Fusco
>
> Getting the following exception while trying to implement Drools in Android.
> 06-08 12:25:41.660 19177-19177/com.example.admin23.droolstest W/System.err: java.lang.RuntimeException: Unable to instantiate object for class 'org.drools.android.DexPackageClassLoader' with constructor public org.drools.android.DexPackageClassLoader(org.drools.core.rule.JavaDialectRuntimeData,java.lang.ClassLoader)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.core.util.ClassUtils.instantiateObject(ClassUtils.java:272)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.core.rule.JavaDialectRuntimeData.makeClassLoader(JavaDialectRuntimeData.java:618)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.core.rule.JavaDialectRuntimeData.onAdd(JavaDialectRuntimeData.java:243)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.rule.builder.dialect.java.JavaDialect.<init>(JavaDialect.java:187)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.newDialect(JavaDialectConfiguration.java:91)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.buildDialectRegistry(KnowledgeBuilderConfigurationImpl.java:392)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.compiler.PackageRegistry.<init>(PackageRegistry.java:55)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.newPackage(KnowledgeBuilderImpl.java:1571)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.initPackageRegistry(KnowledgeBuilderImpl.java:1044)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.createPackageRegistry(KnowledgeBuilderImpl.java:1015)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.initPackageRegistries(CompositeKnowledgeBuilderImpl.java:297)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildPackages(CompositeKnowledgeBuilderImpl.java:116)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:105)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:244)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:64)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:230)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:198)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at com.example.admin23.droolstest.MainActivity.onCreate(MainActivity.java:143)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at android.app.Activity.performCreate(Activity.java:6876)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1135)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3206)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3349)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at android.app.ActivityThread.access$1100(ActivityThread.java:221)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1794)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at android.os.Handler.dispatchMessage(Handler.java:102)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at android.os.Looper.loop(Looper.java:158)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at android.app.ActivityThread.main(ActivityThread.java:7224)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at java.lang.reflect.Method.invoke(Native Method)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: Caused by: java.lang.reflect.InvocationTargetException
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at java.lang.reflect.Constructor.newInstance(Native Method)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.core.util.ClassUtils.instantiateObject(ClassUtils.java:270)
> 06-08 12:25:41.670 19177-19177/com.example.admin23.droolstest W/System.err: ... 29 more
> 06-08 12:25:41.680 19177-19177/com.example.admin23.droolstest W/System.err: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.io.File.getAbsolutePath()' on a null object reference
> 06-08 12:25:41.680 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.android.MultiDexClassLoader.<init>(MultiDexClassLoader.java:70)
> 06-08 12:25:41.680 19177-19177/com.example.admin23.droolstest W/System.err: at org.drools.android.DexPackageClassLoader.<init>(DexPackageClassLoader.java:44)
> 06-08 12:25:41.680 19177-19177/com.example.admin23.droolstest W/System.err: ... 31 more
> Whenever I'm trying to call kieBuilder.buildAll(); method it's giving me the exception rather giving the result array. Please help to resolve this. Any help would be appreciable.
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-8942) Request Scope is not active during Batchlet
by Cheng Fang (JIRA)
[ https://issues.jboss.org/browse/WFLY-8942?page=com.atlassian.jira.plugin.... ]
Cheng Fang reassigned WFLY-8942:
--------------------------------
Assignee: James Perkins (was: Cheng Fang)
> Request Scope is not active during Batchlet
> -------------------------------------------
>
> Key: WFLY-8942
> URL: https://issues.jboss.org/browse/WFLY-8942
> Project: WildFly
> Issue Type: Bug
> Components: Batch, CDI / Weld
> Affects Versions: 10.1.0.Final
> Environment: Wildfly 10.1.0 Final
> Reporter: Cody Lerum
> Assignee: James Perkins
>
> When executing a Java EE 7 batchlet if an injection of an @RequestScoped bean is attempted.
> Example
> {noformat}
> 20:57:13,995 WARN [org.jberet] (Batch Thread - 13) JBERET000001: Failed to run batchlet org.jberet.job.model.RefArtifact@b5b6a97: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:689)
> at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:90)
> at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:165)
> at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:83)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-8942) Request Scope is not active during Batchlet
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-8942?page=com.atlassian.jira.plugin.... ]
James Perkins commented on WFLY-8942:
-------------------------------------
I don't think there's a context in the same type of context in CDI as there are for the other two. I'll have to look at CDI to remember how the context there works. It's been a while since I've looked. Feel free to reassign this to me if you need me to look.
FWIW I think we don't quite handle CDI correctly with the, WFLY-3424. This issue could be a result of that.
> Request Scope is not active during Batchlet
> -------------------------------------------
>
> Key: WFLY-8942
> URL: https://issues.jboss.org/browse/WFLY-8942
> Project: WildFly
> Issue Type: Bug
> Components: Batch, CDI / Weld
> Affects Versions: 10.1.0.Final
> Environment: Wildfly 10.1.0 Final
> Reporter: Cody Lerum
> Assignee: Cheng Fang
>
> When executing a Java EE 7 batchlet if an injection of an @RequestScoped bean is attempted.
> Example
> {noformat}
> 20:57:13,995 WARN [org.jberet] (Batch Thread - 13) JBERET000001: Failed to run batchlet org.jberet.job.model.RefArtifact@b5b6a97: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:689)
> at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:90)
> at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:165)
> at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:83)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-8942) Request Scope is not active during Batchlet
by Cheng Fang (JIRA)
[ https://issues.jboss.org/browse/WFLY-8942?page=com.atlassian.jira.plugin.... ]
Cheng Fang commented on WFLY-8942:
----------------------------------
[~jamezp], when starting a batch job, do we propagate the CDI context, the same way we do with naming context and security context?
> Request Scope is not active during Batchlet
> -------------------------------------------
>
> Key: WFLY-8942
> URL: https://issues.jboss.org/browse/WFLY-8942
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Affects Versions: 10.1.0.Final
> Environment: Wildfly 10.1.0 Final
> Reporter: Cody Lerum
> Assignee: Cheng Fang
>
> When executing a Java EE 7 batchlet if an injection of an @RequestScoped bean is attempted.
> Example
> {noformat}
> 20:57:13,995 WARN [org.jberet] (Batch Thread - 13) JBERET000001: Failed to run batchlet org.jberet.job.model.RefArtifact@b5b6a97: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:689)
> at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:90)
> at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:165)
> at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:83)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-8942) Request Scope is not active during Batchlet
by Cheng Fang (JIRA)
[ https://issues.jboss.org/browse/WFLY-8942?page=com.atlassian.jira.plugin.... ]
Cheng Fang updated WFLY-8942:
-----------------------------
Component/s: CDI / Weld
> Request Scope is not active during Batchlet
> -------------------------------------------
>
> Key: WFLY-8942
> URL: https://issues.jboss.org/browse/WFLY-8942
> Project: WildFly
> Issue Type: Bug
> Components: Batch, CDI / Weld
> Affects Versions: 10.1.0.Final
> Environment: Wildfly 10.1.0 Final
> Reporter: Cody Lerum
> Assignee: Cheng Fang
>
> When executing a Java EE 7 batchlet if an injection of an @RequestScoped bean is attempted.
> Example
> {noformat}
> 20:57:13,995 WARN [org.jberet] (Batch Thread - 13) JBERET000001: Failed to run batchlet org.jberet.job.model.RefArtifact@b5b6a97: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:689)
> at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:90)
> at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:165)
> at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:83)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2968) Servers in a domain won't boot if local auth is disabled on the host controller
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2968?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-2968:
----------------------------------
Fix Version/s: 3.0.0.CR1
> Servers in a domain won't boot if local auth is disabled on the host controller
> -------------------------------------------------------------------------------
>
> Key: WFCORE-2968
> URL: https://issues.jboss.org/browse/WFCORE-2968
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: James Perkins
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Beta27
>
>
> If local authentication has been disabled on the host controller servers cannot communicate with the host controller and fail to start.
> {code}
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] ... 4 more
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:188)
> [Server:server-one] at org.jboss.as.server.ServerService.boot(ServerService.java:387)
> [Server:server-one] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] Caused by: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:113)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:95)
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:185)
> [Server:server-one] ... 3 more
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,243 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> [Server:server-one] 15:10:51,254 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 3.0.0.Beta27-SNAPSHOT "Kenny" stopped in 6ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months