January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5971) Weld's ProxyServicesImpl#getClassLoader has reversed security manager check

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-5971: ------------------------------------ Summary: Weld's ProxyServicesImpl#getClassLoader has reversed security manager check Key: WFLY-5971 URL: https://issues.jboss.org/browse/WFLY-5971 Project: WildFly Issue Type: Bug Components: CDI / Weld Affects Versions: 10.0.0.CR5 Reporter: Radoslav Husar Assignee: Radoslav Husar Introduced by 9362aab078aa0b61144b27f9a0ae9b233bcde9ca Method org.jboss.as.weld.services.bootstrap.ProxyServicesImpl#getClassLoader Stack trace https://gist.github.com/rhusar/2db92caf6e3bd182331f -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4769) WildFly 8 and 9. Connecting to topic using http-remoting and JNDI fails when server is behind NAT firewall

by jukka sirviö (JIRA)

[ https://issues.jboss.org/browse/WFLY-4769?page=com.atlassian.jira.plugin.... ] jukka sirviö commented on WFLY-4769: ------------------------------------ Please see the forum reference, there are the related steps how to go-around this in JMS client. > WildFly 8 and 9. Connecting to topic using http-remoting and JNDI fails when server is behind NAT firewall > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-4769 > URL: https://issues.jboss.org/browse/WFLY-4769 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.2.0.Final, 9.0.0.CR1 > Environment: RedHat7 > Reporter: George Turner > Assignee: Jeff Mesnil > > Server is behind NAT firewall. Client code: > Properties topicProperties = new Properties(); > topicProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); > topicProperties.put(Context.PROVIDER_URL, "http-remoting://" + host + ":" + port); > InitialContext ctx = new InitialContext(topicProperties); > ConnectionFactory tmp = (ConnectionFactory) topicCtx.lookup("jms/RemoteConnectionFactory"); > connection = tmp.createConnection(); > Jun 11, 2015 8:26:07 AM org.xnio.Xnio <clinit> > INFO: XNIO version 3.3.1.Final > Jun 11, 2015 8:26:07 AM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.3.1.Final > Jun 11, 2015 8:26:07 AM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 4.0.9.Final > javax.jms.JMSException: Failed to create session factory > at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:673) > at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:112) > at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:107) > at com.lmco.spacefence.netcentric.test.client.TestMessageConsumer.<init>(TestMessageConsumer.java:36) > at com.lmco.spacefence.netcentric.test.client.TestMessageConsumer.main(TestMessageConsumer.java:24) > Caused by: HornetQNotConnectedException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.] > at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:905) > at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:669) > ... 4 more > Disconnected from the target VM, address: '127.0.0.1:54275', transport: 'socket' > > Client debugger shows the ConnectionFactory instance returned: > initialConnectors = {org.hornetq.api.core.TransportConfiguration[1]@2183} > 0 = {org.hornetq.api.core.TransportConfiguration@2196} "TransportConfiguration(name=http-connector, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8080&host=10-10-20-77&http-upgrade-enabled=true&http-upgrade-endpoint=http-acceptor" > name = {java.lang.String@2198} "http-connector" > factoryClassName = {java.lang.String@2199} "org.hornetq.core.remoting.impl.netty.NettyConnectorFactory" > params = {java.util.HashMap@2200} size = 4 > 0 = {java.util.HashMap$Node@2203} "port" -> "8080" > 1 = {java.util.HashMap$Node@2204} "host" -> "10.10.20.77" > 2 = {java.util.HashMap$Node@2205} "http-upgrade-enabled" -> "true" > 3 = {java.util.HashMap$Node@2206} "http-upgrade-endpoint" -> "http-acceptor" > 10.10.20.77 is IP address of server behind firewall, NOT the IP address used by the client. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1022) WebSphere: unable to deploy Kie server war

by Karel Suta (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1022?page=com.atlassian.jira.plugi... ] Karel Suta updated DROOLS-1022: ------------------------------- Labels: reported-by-qe (was: ) > WebSphere: unable to deploy Kie server war > ------------------------------------------ > > Key: DROOLS-1022 > URL: https://issues.jboss.org/browse/DROOLS-1022 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.4.x > Environment: WebSphere Platform 8.5.5.7 > Kie server 6.4.0-SNAPSHOT > Reporter: Karel Suta > Assignee: Maciej Swiderski > Labels: reported-by-qe > Attachments: SystemOut.log > > > When I try to deploy latest Kie server on WebSphere I get exception listed in log. This error also prevents user from logging into WebSphere console (with error: "SECJ0118E: Authentication error during authentication for user xxx") > In 6.3.1-SNAPSHOT deployment works without issue. > Issue may be related xercesImpl which was missing in 6.3.1 and is present in 6.4. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1022) WebSphere: unable to deploy Kie server war

by Karel Suta (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1022?page=com.atlassian.jira.plugi... ] Karel Suta updated DROOLS-1022: ------------------------------- Labels: (was: qe) > WebSphere: unable to deploy Kie server war > ------------------------------------------ > > Key: DROOLS-1022 > URL: https://issues.jboss.org/browse/DROOLS-1022 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.4.x > Environment: WebSphere Platform 8.5.5.7 > Kie server 6.4.0-SNAPSHOT > Reporter: Karel Suta > Assignee: Maciej Swiderski > Attachments: SystemOut.log > > > When I try to deploy latest Kie server on WebSphere I get exception listed in log. This error also prevents user from logging into WebSphere console (with error: "SECJ0118E: Authentication error during authentication for user xxx") > In 6.3.1-SNAPSHOT deployment works without issue. > Issue may be related xercesImpl which was missing in 6.3.1 and is present in 6.4. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1022) WebSphere: unable to deploy Kie server war

by Karel Suta (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1022?page=com.atlassian.jira.plugi... ] Karel Suta updated DROOLS-1022: ------------------------------- Labels: qe (was: ) > WebSphere: unable to deploy Kie server war > ------------------------------------------ > > Key: DROOLS-1022 > URL: https://issues.jboss.org/browse/DROOLS-1022 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.4.x > Environment: WebSphere Platform 8.5.5.7 > Kie server 6.4.0-SNAPSHOT > Reporter: Karel Suta > Assignee: Maciej Swiderski > Labels: qe > Attachments: SystemOut.log > > > When I try to deploy latest Kie server on WebSphere I get exception listed in log. This error also prevents user from logging into WebSphere console (with error: "SECJ0118E: Authentication error during authentication for user xxx") > In 6.3.1-SNAPSHOT deployment works without issue. > Issue may be related xercesImpl which was missing in 6.3.1 and is present in 6.4. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1022) WebSphere: unable to deploy Kie server war

by Karel Suta (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1022?page=com.atlassian.jira.plugi... ] Karel Suta reassigned DROOLS-1022: ---------------------------------- Assignee: Maciej Swiderski (was: Edson Tirelli) > WebSphere: unable to deploy Kie server war > ------------------------------------------ > > Key: DROOLS-1022 > URL: https://issues.jboss.org/browse/DROOLS-1022 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.4.x > Environment: WebSphere Platform 8.5.5.7 > Kie server 6.4.0-SNAPSHOT > Reporter: Karel Suta > Assignee: Maciej Swiderski > Labels: qe > Attachments: SystemOut.log > > > When I try to deploy latest Kie server on WebSphere I get exception listed in log. This error also prevents user from logging into WebSphere console (with error: "SECJ0118E: Authentication error during authentication for user xxx") > In 6.3.1-SNAPSHOT deployment works without issue. > Issue may be related xercesImpl which was missing in 6.3.1 and is present in 6.4. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5969) io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5969?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-5969: ----------------------------------- What platform is this? > io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents > ---------------------------------------------------------------------------------- > > Key: WFLY-5969 > URL: https://issues.jboss.org/browse/WFLY-5969 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Reporter: Matthew Casperson > Assignee: Stuart Douglas > Attachments: Screen Shot 2016-01-11 at 11.24.34 am.png, Screen Shot 2016-01-11 at 11.24.41 am.png > > > The Untertow DefaultServlet exhibits some odd behaviour when it has been mapped to a subdirectory. > To see this behaviour, build the WAR file from the sample project at https://github.com/mcasperson/wildfly-default-servlet-bug. Deploy to WildFly 10 CR5, and open the link http://localhost:8080/wildfly-default-servlet-bug/static (note no slash on the end of the URL). You'll see the expected directory listing. > !Screen Shot 2016-01-11 at 11.24.41 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/ (note the slash on the end). You'll actually now be browsing the root directory of the application. > !Screen Shot 2016-01-11 at 11.24.34 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml (note the double static in the URL). You'll be able to open the XML file. This is not what I would have expected. > Now open http://localhost:8080/wildfly-default-servlet-bug/static/data.xml. You'll get a 404. I would have expected to be able to open the file using this URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5959) Infinispan caches non transactional despite transactional cache mode

by Alexander Slack (JIRA)

[ https://issues.jboss.org/browse/WFLY-5959?page=com.atlassian.jira.plugin.... ] Alexander Slack edited comment on WFLY-5959 at 1/11/16 5:24 AM: ---------------------------------------------------------------- I confirm that injecting the cache directly solves the problem (it reports the transaction mode as TRANSACTIONAL). Thank you for investigating the issue. was (Author: alexslackx): I confirm that injecting the cache directly solves the problem (it reports the transaction mode as TRANSACTIONAL). Thanks you for investigating the issue. > Infinispan caches non transactional despite transactional cache mode > -------------------------------------------------------------------- > > Key: WFLY-5959 > URL: https://issues.jboss.org/browse/WFLY-5959 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR5 > Reporter: Alexander Slack > Assignee: Paul Ferraro > > Local Infinispan caches declared in standalone.xml are no longer set as transactional even if a transactional mode is selected. > This prevents creation of atomic maps using AtomicMapLookup as that specifically checks if the cache is transactional (throws java.lang.IllegalStateException: AtomicMap needs a transactional cache.) > Possibly caused by issue WFLY-5327. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5959) Infinispan caches non transactional despite transactional cache mode

by Alexander Slack (JIRA)

[ https://issues.jboss.org/browse/WFLY-5959?page=com.atlassian.jira.plugin.... ] Alexander Slack commented on WFLY-5959: --------------------------------------- I confirm that injecting the cache directly solves the problem (it reports the transaction mode as TRANSACTIONAL). Thanks you for investigating the issue. > Infinispan caches non transactional despite transactional cache mode > -------------------------------------------------------------------- > > Key: WFLY-5959 > URL: https://issues.jboss.org/browse/WFLY-5959 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR5 > Reporter: Alexander Slack > Assignee: Paul Ferraro > > Local Infinispan caches declared in standalone.xml are no longer set as transactional even if a transactional mode is selected. > This prevents creation of atomic maps using AtomicMapLookup as that specifically checks if the cache is transactional (throws java.lang.IllegalStateException: AtomicMap needs a transactional cache.) > Possibly caused by issue WFLY-5327. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1274) CLI resolve-parameter-values set to true does not recognise vaulted strings

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1274?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1274: ------------------------------------------------- Lin Gao <lgao(a)redhat.com> changed the Status of [bug 1286677|https://bugzilla.redhat.com/show_bug.cgi?id=1286677] from NEW to CLOSED > CLI resolve-parameter-values set to true does not recognise vaulted strings > --------------------------------------------------------------------------- > > Key: WFCORE-1274 > URL: https://issues.jboss.org/browse/WFCORE-1274 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.5.Final > Reporter: Lin Gao > Assignee: Lin Gao > > When enabling > <resolve-parameter-values>true</resolve-parameter-values> > in "bin\jboss-cli.xml" > vaulted string will get misinterpreted. > Example, if a command has "${VAULT::tom::tom::1}" then > the parser sees this as ${name:defaultValue} with > name="VAULT" > defaultValue=":tom::tom::1" > Escaping the $ sign in various ways did not help. The only way is to switch <resolve-parameter-values> back to false. > Ideally, the parser should recognize vaulted string and pass then in unchanged. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 2016