March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4324) While starting Jboss AS getting IllegalStateException.

by ANKUSH NIKHAR (JIRA)

[ https://issues.jboss.org/browse/WFLY-4324?page=com.atlassian.jira.plugin.... ] ANKUSH NIKHAR commented on WFLY-4324: ------------------------------------- [~ctomc] Hi Cerar, As I am new to JBOSS WildFly, so could you please tell me how can I update the jandex version. In My project pom.xml I dont have jandex dependency, may be it is configured in the JBOSS somewhere. So please guide me on the same. > While starting Jboss AS getting IllegalStateException. > ------------------------------------------------------ > > Key: WFLY-4324 > URL: https://issues.jboss.org/browse/WFLY-4324 > Project: WildFly > Issue Type: Bug > Environment: Java with 1.8 v and JBOS 7 > Reporter: ANKUSH NIKHAR > > Hi, > I am facing issue when I am trying to deploy web service on Jboss 7 and using jdk 1.8 version. Below are the sample log : > This issue does not impact the processing of my code execution. Is this just warning or will it harm in future. > I am migrating my project from jdk1.7 to 1.8. > When I try to deploy WS with jdk1.7, I didn't get such error. > 18:56:01,032 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015852: Could not index class sun/applet/AppletPanel.class at /D:/Test Eclipse/Migration Eclipse/Mig Workspace/CDLibrary/CDLibrary-test/content/InMemory.war/WEB-INF/lib/tools.jar: java.lang.IllegalStateException: Unknown tag! pos=1006 poolCount = 1018 > at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:606) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] > at org.jboss.jandex.Indexer.index(Indexer.java:640) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] > at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:100) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4313) Clean-up tests which use Kerberos in the WildFly testsuite

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4313?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4313: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1189141|https://bugzilla.redhat.com/show_bug.cgi?id=1189141] from ON_QA to VERIFIED > Clean-up tests which use Kerberos in the WildFly testsuite > ---------------------------------------------------------- > > Key: WFLY-4313 > URL: https://issues.jboss.org/browse/WFLY-4313 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > Clean up Kerberos tests and add an unified logic for skipping Kerberos test configurations which proved to be unstable/buggy. By a configuration here is meant combination of Java vendor, version and IP stack. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4376) Incorrect callback handler used during authentication (SASL)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4376?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4376: ----------------------------------------------- Enrique Gonzalez Martinez <egonzale(a)redhat.com> changed the Status of [bug 996897|https://bugzilla.redhat.com/show_bug.cgi?id=996897] from NEW to ASSIGNED > Incorrect callback handler used during authentication (SASL) > ------------------------------------------------------------- > > Key: WFLY-4376 > URL: https://issues.jboss.org/browse/WFLY-4376 > Project: WildFly > Issue Type: Bug > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > > Cluster topology messages are not using the proper callbackhandler when the connection is being established. > {code} > 06:59:44,609 ERROR [org.jboss.remoting.remote.connection] (Remoting "config-based-ejb-client-endpoint" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > 06:59:44,611 INFO [org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager] (ejb-client-cluster-node-connection-creation-2-thread-2) Could not create a connection for cluster node ClusterNode{clusterName='ejb', nodeName='perf18', clientMappings=[ClientMapping{sourceNetworkAddress=/0:0:0:0:0:0:0:0, sourceNetworkMaskBits=0, destinationAddress='10.16.90.54', destinationPort=4447}], resolvedDestination=[Destination address=10.16.90.54, destination port=4447]} in cluster ejb > java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:91) > at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:89) > at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:406) > at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:380) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:382) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:225) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:187) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:386) > at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:151) > at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:132) > at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:87) > ... 7 more > {code} > Before that, this log is produced: > {code} > DEBUG: Client authentication failed for mechanism DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Cannot perform callback to acquire realm, authentication ID or password [Caused by javax.security.auth.callback.UnsupportedCallbackException] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1119) Assign an unique NodeID automatically

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-1119?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-1119: ------------------------------------- Ah great, thanks Amos (assuming you meant "max length of thenode_identifier **28** is OK") > Assign an unique NodeID automatically > ------------------------------------- > > Key: WFLY-1119 > URL: https://issues.jboss.org/browse/WFLY-1119 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Clebert Suconic > Assignee: Amos Feng > Priority: Optional > > It shouldn't be needed to assign the node-id manually IMO. > You could store the node-id on a file and recover it for subsequent starts. > On hornetQ for instance, we look for the nodeID on a file, if the file doesn't exist we assign a UUID and write to the file. > In our previous experience UUID would be a best fit to assign the nodes since that was the only way we could guarantee unique IDs between the nodes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-576) Upgrade jboss-remoting to release that has fix for REM3-204

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-576?page=com.atlassian.jira.plugin... ] Tomaz Cerar updated WFCORE-576: ------------------------------- Summary: Upgrade jboss-remoting to release that has fix for REM3-204 (was: Upgrade jboss-remoting to 4.0.8.Final) > Upgrade jboss-remoting to release that has fix for REM3-204 > ----------------------------------------------------------- > > Key: WFCORE-576 > URL: https://issues.jboss.org/browse/WFCORE-576 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Test Suite > Affects Versions: 1.0.0.Alpha19 > Reporter: ehsavoie Hugonnet > Assignee: Tomaz Cerar > Fix For: 1.0.0.Beta1 > > > In order to fix WFCORE-487 we need to have a new version of jboss-remoting with the fix for REM3-204 integrated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-576) Upgrade jboss-remoting to release that has fix for REM3-204

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-576?page=com.atlassian.jira.plugin... ] Tomaz Cerar reassigned WFCORE-576: ---------------------------------- Assignee: David Lloyd (was: Tomaz Cerar) > Upgrade jboss-remoting to release that has fix for REM3-204 > ----------------------------------------------------------- > > Key: WFCORE-576 > URL: https://issues.jboss.org/browse/WFCORE-576 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Test Suite > Affects Versions: 1.0.0.Alpha19 > Reporter: ehsavoie Hugonnet > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > > In order to fix WFCORE-487 we need to have a new version of jboss-remoting with the fix for REM3-204 integrated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-576) Upgrade jboss-remoting to release that has fix for REM3-204

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-576?page=com.atlassian.jira.plugin... ] Tomaz Cerar updated WFCORE-576: ------------------------------- Fix Version/s: 1.0.0.Beta1 > Upgrade jboss-remoting to release that has fix for REM3-204 > ----------------------------------------------------------- > > Key: WFCORE-576 > URL: https://issues.jboss.org/browse/WFCORE-576 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Test Suite > Affects Versions: 1.0.0.Alpha19 > Reporter: ehsavoie Hugonnet > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > > In order to fix WFCORE-487 we need to have a new version of jboss-remoting with the fix for REM3-204 integrated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-576) Upgrade jboss-remoting to release that has fix for REM3-204

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-576?page=com.atlassian.jira.plugin... ] Tomaz Cerar commented on WFCORE-576: ------------------------------------ That will help us greatly with stability of few tests > Upgrade jboss-remoting to release that has fix for REM3-204 > ----------------------------------------------------------- > > Key: WFCORE-576 > URL: https://issues.jboss.org/browse/WFCORE-576 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Test Suite > Affects Versions: 1.0.0.Alpha19 > Reporter: ehsavoie Hugonnet > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > > In order to fix WFCORE-487 we need to have a new version of jboss-remoting with the fix for REM3-204 integrated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-576) Upgrade jboss-remoting to 4.0.8.Final

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-576: ---------------------------------------- Summary: Upgrade jboss-remoting to 4.0.8.Final Key: WFCORE-576 URL: https://issues.jboss.org/browse/WFCORE-576 Project: WildFly Core Issue Type: Component Upgrade Components: Test Suite Affects Versions: 1.0.0.Alpha19 Reporter: ehsavoie Hugonnet Assignee: Tomaz Cerar In order to fix WFCORE-487 we need to have a new version of jboss-remoting with the fix for REM3-204 integrated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-310) Allow servlets to be marked overridable via Servlet registration API

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-310?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-310: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1196513|https://bugzilla.redhat.com/show_bug.cgi?id=1196513] from NEW to ASSIGNED > Allow servlets to be marked overridable via Servlet registration API > -------------------------------------------------------------------- > > Key: JBWEB-310 > URL: https://issues.jboss.org/browse/JBWEB-310 > Project: JBoss Web > Issue Type: Enhancement > Affects Versions: JBossWeb-7.5.0.GA > Reporter: James Livingston > Assignee: Remy Maucherat > Attachments: JBWEB-310.patch > > > To resolve https://bugzilla.redhat.com/show_bug.cgi?id=1094248, JBossWeb needs to add an 'overridable' flag on Wrapper, and not treat new mappings as conflicting if the one previously using the mapping was marked overridable. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

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 March 2015