August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2061) TYPE_STRING does not handle unicode

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2061?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2061: -------------------------------- Excellent! I'm trying to close this issue but JIRA seems to disallow me to do that... :-) Can you close it? > TYPE_STRING does not handle unicode > ----------------------------------- > > Key: JGRP-2061 > URL: https://issues.jboss.org/browse/JGRP-2061 > Project: JGroups > Issue Type: Bug > Reporter: Cody Ebberson > Assignee: Bela Ban > Fix For: 4.0.6 > > > In several places throughout the org.jgroups.util.Util class, it is assumed that Strings are one byte per character. > For example, see objectToByteBuffer lines 561-567: > https://github.com/belaban/JGroups/blob/master/src/org/jgroups/util/Util.... > {code:java} > case TYPE_STRING: > String str=(String)obj; > int len=str.length(); > ByteBuffer retval=ByteBuffer.allocate(Global.BYTE_SIZE + len).put(TYPE_STRING); > for(int i=0; i < len; i++) > retval.put((byte)str.charAt(i)); > return retval.array(); > {code} > This code will incorrectly encode any String with non ASCII encoding. > There are several options to fix. You could use str.getBytes(StandardCharsets.UTF_8) to get a proper byte encoding, or you could use the existing TYPE_SERIALIZABLE code path. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9275) unable to invoke server1 EJB via server2

by Loren Chang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9275?page=com.atlassian.jira.plugin.... ] Loren Chang updated WFLY-9275: ------------------------------ Summary: unable to invoke server1 EJB via server2 (was: invoke server1 EJB via server2 Fail) > unable to invoke server1 EJB via server2 > ---------------------------------------- > > Key: WFLY-9275 > URL: https://issues.jboss.org/browse/WFLY-9275 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Loren Chang > Attachments: EJBTest.png, EJBTest.zip, WildFlyBug.png > > > This test code on "public static void main" is ok, but fail on war/ear > EJB client API Version:wildfly-naming-client-1.0.0.Beta13.jar、jboss-remote-naming-2.0.4.Final.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9275) invoke server1 EJB via server2 Fail

by Loren Chang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9275?page=com.atlassian.jira.plugin.... ] Loren Chang updated WFLY-9275: ------------------------------ Attachment: EJBTest.png > invoke server1 EJB via server2 Fail > ----------------------------------- > > Key: WFLY-9275 > URL: https://issues.jboss.org/browse/WFLY-9275 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Loren Chang > Attachments: EJBTest.png, EJBTest.zip, WildFlyBug.png > > > This test code on "public static void main" is ok, but fail on war/ear > EJB client API Version:wildfly-naming-client-1.0.0.Beta13.jar、jboss-remote-naming-2.0.4.Final.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9275) invoke server1 EJB via server2 Fail

by Loren Chang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9275?page=com.atlassian.jira.plugin.... ] Loren Chang updated WFLY-9275: ------------------------------ Attachment: EJBTest.zip > invoke server1 EJB via server2 Fail > ----------------------------------- > > Key: WFLY-9275 > URL: https://issues.jboss.org/browse/WFLY-9275 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Loren Chang > Attachments: EJBTest.png, EJBTest.zip, WildFlyBug.png > > > This test code on "public static void main" is ok, but fail on war/ear > EJB client API Version:wildfly-naming-client-1.0.0.Beta13.jar、jboss-remote-naming-2.0.4.Final.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9275) invoke server1 EJB via server2 Fail

by Loren Chang (JIRA)

[ https://issues.jboss.org/browse/WFLY-9275?page=com.atlassian.jira.plugin.... ] Loren Chang updated WFLY-9275: ------------------------------ Summary: invoke server1 EJB via server2 Fail (was: EJB client(on ear/war) lookup remote SessionBean on multi server fail, all request recieved by one server(client)) > invoke server1 EJB via server2 Fail > ----------------------------------- > > Key: WFLY-9275 > URL: https://issues.jboss.org/browse/WFLY-9275 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Loren Chang > Attachments: WildFlyBug.png > > > This test code on "public static void main" is ok, but fail on war/ear > EJB client API Version:wildfly-naming-client-1.0.0.Beta13.jar、jboss-remote-naming-2.0.4.Final.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-171) Add a PlatformLoggingMXBean implementation

by James Perkins (JIRA)

James Perkins created LOGMGR-171: ------------------------------------ Summary: Add a PlatformLoggingMXBean implementation Key: LOGMGR-171 URL: https://issues.jboss.org/browse/LOGMGR-171 Project: JBoss Log Manager Issue Type: Enhancement Reporter: James Perkins Assignee: James Perkins The {{LoggingMXBean}} is deprecated in Java 9. The {{PlatformLoggingMXBean}} has been available since Java 7 and should be implemented to be better context aware for JBoss Log Manager. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3214) PathInfoHandler should lazy create its DateTimeFormatter and ZoneId

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3214: ---------------------------------------- Summary: PathInfoHandler should lazy create its DateTimeFormatter and ZoneId Key: WFCORE-3214 URL: https://issues.jboss.org/browse/WFCORE-3214 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Profiling shows that PathInfoHandler's creation of a DateTimeFormatter and a ZoneId takes about 15ms. There's no need to do that during <clinit> which happens during boot; it can be deferred until the handler is used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9283) Clarify community documentation for ignore-unused-configuration

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-9283?page=com.atlassian.jira.plugin.... ] Ken Wills reassigned WFLY-9283: ------------------------------- Assignee: Ken Wills > Clarify community documentation for ignore-unused-configuration > --------------------------------------------------------------- > > Key: WFLY-9283 > URL: https://issues.jboss.org/browse/WFLY-9283 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Minor > > Current Wildfly documentation uses "ignore unused resources" around the documented sections for ignore-unused-configuration: > https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-Ignor... > This should be changed to be less confusing by just using the configuration term outside of the initial description. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9283) Clarify community documentation for ignore-unused-configuration

by Ken Wills (JIRA)

Ken Wills created WFLY-9283: ------------------------------- Summary: Clarify community documentation for ignore-unused-configuration Key: WFLY-9283 URL: https://issues.jboss.org/browse/WFLY-9283 Project: WildFly Issue Type: Task Components: Documentation Reporter: Ken Wills Priority: Minor Current Wildfly documentation uses "ignore unused resources" around the documented sections for ignore-unused-configuration: https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-Ignor... This should be changed to be less confusing by just using the configuration term outside of the initial description. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9281) Unable to remove an installed resource adapter

by John Huntley (JIRA)

[ https://issues.jboss.org/browse/WFLY-9281?page=com.atlassian.jira.plugin.... ] John Huntley commented on WFLY-9281: ------------------------------------ >From my reading of the source code I suspect that the problem is a result of the code changes introduced by WFCORE-2849 and that org.jboss.as.connector.subsystems.resourceadapters.RaRemove.java now needs an update around line 156. I did a search of this Jira project but was unable to find any other tickets referring to RaRemove that are current. > Unable to remove an installed resource adapter > ---------------------------------------------- > > Key: WFLY-9281 > URL: https://issues.jboss.org/browse/WFLY-9281 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 11.0.0.CR1 > Reporter: John Huntley > Assignee: Stefano Maestri > Attachments: wf11-ra-error.txt > > > Running a :remove operation for a defined resource adapter fails with error WFLYCTL0123. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 August 2017