March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3187) Can't deploy same webservice endpoint impl with different url pattern

by Jim Ma (JIRA)

Jim Ma created WFLY-3187: ---------------------------- Summary: Can't deploy same webservice endpoint impl with different url pattern Key: WFLY-3187 URL: https://issues.jboss.org/browse/WFLY-3187 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Reporter: Jim Ma Assignee: Jim Ma Fix For: 8.0.1.Final After WFLY-3067 change, CustomerServiceImpl can only be deployed with address http://localhost:8080/webcontext/test1. It should be started with /test2 urlPattern too. {code:xml} <?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4"> <servlet> <servlet-name>TestService</servlet-name> <servlet-class>org.jboss.test.ws.jaxws.samples.webresult.CustomerServiceImpl</servlet-class> </servlet> <servlet-mapping> <servlet-name>TestService</servlet-name> <url-pattern>/test1/*</url-pattern> </servlet-mapping> <servlet> <servlet-name>TestService2</servlet-name> <servlet-class>org.jboss.test.ws.jaxws.samples.webresult.CustomerServiceImpl</servlet-class> </servlet> <servlet-mapping> <servlet-name>TestService2</servlet-name> <url-pattern>/test2/*</url-pattern> </servlet-mapping> </web-app> {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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-812) Release JBoss Negotiation 2.3.0.CR1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-812?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-812: -------------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1081607|https://bugzilla.redhat.com/show_bug.cgi?id=1081607] from POST to MODIFIED > Release JBoss Negotiation 2.3.0.CR1 > ----------------------------------- > > Key: SECURITY-812 > URL: https://issues.jboss.org/browse/SECURITY-812 > Project: PicketBox > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_0_CR1 > > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3182) Upgrade to JBoss Negotiation 2.3.0.CR1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3182?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3182: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1081607|https://bugzilla.redhat.com/show_bug.cgi?id=1081607] from POST to MODIFIED > Upgrade to JBoss Negotiation 2.3.0.CR1 > -------------------------------------- > > Key: WFLY-3182 > URL: https://issues.jboss.org/browse/WFLY-3182 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3186) Upgrade to Weld 2.2

by Jozef Hartinger (JIRA)

Jozef Hartinger created WFLY-3186: ------------------------------------- Summary: Upgrade to Weld 2.2 Key: WFLY-3186 URL: https://issues.jboss.org/browse/WFLY-3186 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 8.0.1.Final -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3186) Upgrade to Weld 2.2

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-3186?page=com.atlassian.jira.plugin.... ] Jozef Hartinger updated WFLY-3186: ---------------------------------- Fix Version/s: (was: 8.0.1.Final) > Upgrade to Weld 2.2 > ------------------- > > Key: WFLY-3186 > URL: https://issues.jboss.org/browse/WFLY-3186 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2474) Security subsystem does not handle acl's module properly, and is missing transformer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2474?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2474: ----------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1029938|https://bugzilla.redhat.com/show_bug.cgi?id=1029938] from ON_QA to VERIFIED > Security subsystem does not handle acl's module properly, and is missing transformer > ------------------------------------------------------------------------------------ > > Key: WFLY-2474 > URL: https://issues.jboss.org/browse/WFLY-2474 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > > The parsed add is done for /subsystem=security/security-domain=other/acl=classic/acl-module=acl > However in the acl resource this is called login-module=acl. > WHen marshalling > {code} > <acl> > <acl-module name="acl" code="AclThingy" flag="required" module="test"> > <module-option name="d" value="r"/> > </acl-module> > </acl> > {code} > becomes > {code} > <acl> > <login-module name="acl" code="AclThingy" flag="required" module="test"> > <module-option name="d" value="r"/> > </login-module> > </acl> > {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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3154) Operation which require server reload should check if something was changed

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-3154?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet updated WFLY-3154: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/6091 (was: https://github.com/kabir/wildfly/pull/28) > Operation which require server reload should check if something was changed > ---------------------------------------------------------------------------- > > Key: WFLY-3154 > URL: https://issues.jboss.org/browse/WFLY-3154 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > Description of problem: > Server reload is required even if nothing was actually changed. This could have negative impact on usability of WildFly. > Steps to Reproduce: > - start standalone > - connect to cli > - run: /subsystem=jpa:write-attribute(name=default-extended-persistence-inheritance, value=SHALLOW) > - reload server > - run: /subsystem=jpa:write-attribute(name=default-extended-persistence-inheritance, value=SHALLOW) > Actual results: > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > Expected results: > - reload is not required -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-102) Messages#getBundle() needs to be privileged

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-102?page=com.atlassian.jira.plu... ] Ivo Studensky commented on JBLOGGING-102: ----------------------------------------- I am sorry I was testing with wrong version. > Messages#getBundle() needs to be privileged > ------------------------------------------- > > Key: JBLOGGING-102 > URL: https://issues.jboss.org/browse/JBLOGGING-102 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.1.4.GA, 3.2.0.Beta1 > Reporter: Ivo Studensky > Assignee: James Perkins > Fix For: 3.1.3.GA, 3.2.0.Beta1 > > > It ({{org.jboss.logging.Messages#getBundle(Class<T> type, Locale locale)}}) calls {{type.getClassLoader()}} which requires privileges when running with Security Manager. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1721) AUTH and ENCRYPT protocols configured with plain text passwords

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1721?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1721. ---------------------------- Resolution: Won't Fix > AUTH and ENCRYPT protocols configured with plain text passwords > --------------------------------------------------------------- > > Key: JGRP-1721 > URL: https://issues.jboss.org/browse/JGRP-1721 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Fix For: 3.5 > > > The following parameters of AUTH protocol are stored as plain text: > * keystore_password > The following parameters of ENCRYPT protocol are stored as plain text: > * store_password > * key_password > Example: > {code} > <ENCRYPT key_store_name="defaultStore.keystore" store_password="changeit" alias="myKey"/> > {code} > Requirements for storing passwords: https://docspace.corp.redhat.com/docs/DOC-131628 -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1813) JDBC_PING fails to recover for corruption issue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1813?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1813: --------------------------- Fix Version/s: 3.4.4 > JDBC_PING fails to recover for corruption issue > ----------------------------------------------- > > Key: JGRP-1813 > URL: https://issues.jboss.org/browse/JGRP-1813 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.4 > Environment: Windows 7 > Reporter: Brett Donahue > Assignee: Bela Ban > Priority: Minor > Labels: EOFException, JDBC_PING,, corruption > Fix For: 3.5, 3.4.4 > > > heap space was exhausted and issues occurred. In the end, one node in the cluster must have corrupted the data in the JDBC_PING table. From this point onward, our log is full of these (every two seconds): > 2014 03 23 04:00:25#+0100#ERROR#org.jgroups.protocols.SMP_JDBC_PING##anonymous#Thread-15###Error java.io.EOFException: null > at java.io.DataInputStream.readUnsignedShort(DataInputStream.java:340) > at org.jgroups.stack.IpAddress.readFrom(IpAddress.java:226) > at org.jgroups.util.Util.readAddress(Util.java:929) > at org.jgroups.util.Util.readAddresses(Util.java:1047) > at org.jgroups.protocols.PingData.readFrom(PingData.java:163) > at org.jgroups.util.Util.streamableFromByteBuffer(Util.java:753) > at org.jgroups.protocols.Discovery.deserialize(Discovery.java:625) > at org.jgroups.protocols.JDBC_PING.readAll(JDBC_PING.java:221) > at org.jgroups.protocols.JDBC_PING.readAll(JDBC_PING.java:201) > at org.jgroups.protocols.FILE_PING.fetchClusterMembers(FILE_PING.java:68) > at org.jgroups.protocols.Discovery.sendDiscoveryRequest(Discovery.java:263) > at org.jgroups.protocols.Discovery.findMembers(Discovery.java:227) > at org.jgroups.protocols.Discovery.findInitialMembers(Discovery.java:208) > at org.jgroups.protocols.Discovery.down(Discovery.java:551) > at org.jgroups.protocols.FILE_PING.down(FILE_PING.java:101) > at org.jgroups.protocols.MERGE2.down(MERGE2.java:185) > at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:363) > at org.jgroups.protocols.FD.down(FD.java:307) > at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:84) > at org.jgroups.protocols.BARRIER.down(BARRIER.java:95) > at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:533) > at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:575) > at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:347) > at org.jgroups.protocols.ENCRYPT.down(ENCRYPT.java:925) > at org.jgroups.protocols.pbcast.ClientGmsImpl.findInitialMembers(ClientGmsImpl.java:201) > at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:75) > at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:40) > at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1052) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:340) > at org.jgroups.protocols.FRAG2.down(FRAG2.java:136) > at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:237) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1024) > at org.jgroups.JChannel.down(JChannel.java:760) > at org.jgroups.JChannel._connect(JChannel.java:538) > at org.jgroups.JChannel.connect(JChannel.java:290) > at org.jgroups.JChannel.connect(JChannel.java:275) > at com.sap.mobile.platform.server.cluster.service.impl.ClusterCommunicationsJGroupImpl.startCommunications(ClusterCommunicationsJGroupImpl.java:45) > at com.sap.mobile.platform.server.cluster.service.impl.ClusterCommunicationsJGroupImpl.<init>(ClusterCommunicationsJGroupImpl.java:59) > at com.sap.mobile.platform.server.cluster.service.impl.ClusterServiceImpl.run(ClusterServiceImpl.java:187) > at java.lang.Thread.run(Thread.java:791) -- 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

10 years, 9 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 2014