[JBoss JIRA] (JBASMP-83) ++TechHelp <<: I~855~7O9~2847@@ EPSON. . p.r.i.n.t.e.r Technical S.U.P.P.O.R.T p.h.o.n.e n.u.m.b.e.r, I-855-7O9-2847 EPSON. . p.r.i.n.t.e.r S.U.P.P.O.R.T n.u.m.b.e.r,
by dheeru sherman (JIRA)
dheeru sherman created JBASMP-83:
------------------------------------
Summary: ++TechHelp <<: I~855~7O9~2847@@ EPSON. . p.r.i.n.t.e.r Technical S.U.P.P.O.R.T p.h.o.n.e n.u.m.b.e.r, I-855-7O9-2847 EPSON. . p.r.i.n.t.e.r S.U.P.P.O.R.T n.u.m.b.e.r,
Key: JBASMP-83
URL: https://issues.jboss.org/browse/JBASMP-83
Project: JBoss AS Maven Plugins
Issue Type: Bug
Reporter: dheeru sherman
Assignee: James Perkins
Attachments: TechHelp Dheeru posting 3.pdf
((moti))Call @@@++ USA I8557O92847 EPSON p.r.i.n.t.e.r t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8557O92847 EPSON p.r.i.n.t.e.r t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON printer Tech Support phone number,EPSON technical support phone number 1 I8557O92847 .EPSON Tech Support Number EPSON Tech EPSON tech support, EPSON tech support number, EPSON tech support phone number, EPSON technical support, EPSON technical support number, EPSON technical support phone number, EPSON tech support number, EPSON support number, EPSON Tech support phone number, EPSON support phone number, EPSON technical support phone number, EPSON technical support number,Support Phone Number for EPSON printer Phone Number for EPSON CustomerService Technical Support Telephone Number EPSON printer support number EPSON EPSON printer tech support number EPSON EPSON printer technical support number EPSON EPSON printer technical support phone number EPSON EPSON printer customer service number EPSON EPSON internet security technical support EPSON technical support phone number EPSON EPSON tech support phone number EPSON EPSON customer support phone number I-855-709-2847 EPSON EPSON printer support phone number EPSON EPSON support phone EPSON tech support EPSON customer support EPSON phone support EPSON support number EPSON EPSON technical support EPSON printer customer support phone number EPSON EPSON printer tech support phone number EPSON contact EPSON support EPSON printer technical support phone number ~!~I8557092847++ EPSON EPSON phone number EPSON tech support EPSON support ticket EPSON customer support number EPSON EPSON tech support number EPSON EPSON technical support number EPSON EPSON support center EPSON telephone support call EPSON support EPSON printer support support EPSON EPSON billing support EPSON printer technical support number EPSON support EPSON printer EPSON online support EPSON contact support EPSON printer support number EPSON EPSON printer customer support number EPSON EPSON printer tech support number EPSON support for EPSON EPSON phone number EPSON EPSON customer service phone number EPSON EPSON contact phone number EPSON EPSON printer phone number EPSON EPSON printer customer service phone number EPSON phone number EPSON for EPSON customer service EPSON software phone number EPSON phone number EPSON for EPSON EPSON customer service telephone number EPSON EPSON helpline phone number EPSON EPSON contact number EPSON EPSON customer service number EPSON EPSON customer service phone number ~!~I8557092847++ EPSON us EPSON customer service phone number EPSON usa EPSON telephone number EPSON EPSON phone number EPSON usa EPSON printer contact number EPSON EPSON number EPSON EPSON contact number EPSON usa EPSON printer helpline number EPSON EPSON helpline number EPSON EPSON customer number EPSON EPSON printer customer service number EPSON EPSON contact telephone number EPSON contact number EPSON for EPSON EPSON software contact number EPSON EPSON toll free number EPSON EPSON telephone number EPSON uk EPSON registration number EPSON EPSON toll free number EPSON usa EPSON customer service EPSON software customer service contact EPSON customer service EPSON customer service phone EPSON printer customer service EPSON service EPSON printer technical support EPSON printer customer support EPSON technical support reviews telephone EPSON printer EPSON tech support phone number EPSON EPSON printer tech support phone number EPSON EPSON printer customer service EPSON technical support phone number EPSON EPSON printer free printer support EPSON customer service billing EPSON customer service email address EPSON customer service reviews contact EPSON customer service EPSON tech support number EPSON usa EPSON printer support number EPSON EPSON printer contact number EPSON EPSON customer service phone number EPSON EPSON technical support usa EPSON technical support number EPSON EPSON tech support phone EPSON tech support number EPSON EPSON customer service telephone number EPSON EPSON printer customer support number EPSON EPSON printer phone number EPSON EPSON printer online support EPSON customer service number EPSON EPSON tech support center EPSON customer service EPSON software customer service EPSON customer care number EPSON usa EPSON customer number EPSON EPSON customer support number EPSON EPSON customer care number EPSON EPSON customer care toll free number EPSON EPSON tech support EPSON technical support EPSON printer support EPSON printer tech support EPSON support center EPSON.com customer service EPSON printer customer care number EPSON EPSON customer care EPSON phone number EPSON phone number EPSON for EPSON customer service EPSON phone support EPSON phone number EPSON tech support EPSON support phone number EPSON contact EPSON by phone EPSON contact phone number EPSON EPSON helpline phone number EPSON EPSON printer phone EPSON printer for phone EPSON contact number EPSON EPSON contact support contact EPSON printer EPSON contact number EPSON usa EPSON toll free number EPSON EPSON telephone number EPSON EPSON toll free number EPSON usa EPSON printer support services technical support for printer EPSON EPSON customer service phone number EPSON usa EPSON printer customer care number EPSON usa EPSON customer care number EPSON EPSON customer care center EPSON customer support EPSON customer support phone EPSON customer help EPSON customer & technical support EPSON customer portal EPSON customer care phone number EPSON usa EPSON customer care email EPSON helpline EPSON tech support contact EPSON customer care toll free EPSON printer customer service number EPSON EPSON printer protection norton printer customer service number EPSON EPSON software customer service number EPSON EPSON hotline customer service phone number EPSON EPSON customer service phone number EPSON us how to contact EPSON by email EPSON free phone support EPSON printer technical support number EPSON EPSON printer technical support help desk phone number EPSON EPSON technical support number EPSON toll free number EPSON EPSON printer customer support phone number EPSON EPSON printer customer
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFBUILD-20) allow feature pack to be able to copy individual files
by John Mazzitelli (JIRA)
John Mazzitelli created WFBUILD-20:
--------------------------------------
Summary: allow feature pack to be able to copy individual files
Key: WFBUILD-20
URL: https://issues.jboss.org/browse/WFBUILD-20
Project: WildFly Build Tools
Issue Type: Bug
Reporter: John Mazzitelli
Assignee: Stuart Douglas
Today, the feature pack build xml let's you copy mvn artifacts via copy-artifacts.
But suppose I have individual configuration files (not maven artifacts) that I want placed in the "standalone/configuration" directory (as an example target location). It would be nice for the feature pack XSD to support being able to copy normal files like this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1656) log4j per logging deployment configuration errors are swallowed
by James Perkins (JIRA)
James Perkins created WFCORE-1656:
-------------------------------------
Summary: log4j per logging deployment configuration errors are swallowed
Key: WFCORE-1656
URL: https://issues.jboss.org/browse/WFCORE-1656
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Anything logged through log4j's {{org.apache.log4j.helpers.LogLog}} seems to be swallowed. This includes debug messages if log4j debugging is turned on as well as any warnings or errors found during configuration are not printed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1655) verbose patch info should match in offline and online modes
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created WFCORE-1655:
-----------------------------------------
Summary: verbose patch info should match in offline and online modes
Key: WFCORE-1655
URL: https://issues.jboss.org/browse/WFCORE-1655
Project: WildFly Core
Issue Type: Bug
Components: CLI, Patching
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: 3.0.0.Alpha4
When the CLI is connected to the controller, patch info reflects the outcome of read-resource operation. It could be basic info or extended (--verbose).
In the offline mode though, the only information available is the basic one. It is actually limited by the tool's API, which means it never meant to support --verbose.
This difference is not reflected in the help content of the command and simply looks like an inconsistent behavior of the same command depending on the connection status.
Another issue with the offline mode is that, the current version was not propagated to the CLI and would always read "Unknown" for the user.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1647) Default app-name value of Syslog handler in Audit Logging violates specification
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1647?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-1647:
---------------------------------------
I thanks [~jtymel]. I missed that definition at the bottom.
> Default app-name value of Syslog handler in Audit Logging violates specification
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1647
> URL: https://issues.jboss.org/browse/WFCORE-1647
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha3
> Reporter: Jan Tymel
> Assignee: Ken Wills
> Fix For: 3.0.0.Alpha4, 2.2.0.CR8
>
>
> According to syslog specification[1] {{app-name}} cannot contain space character (" "). However, the default value in WildFly Core 3.0.0.Alpha3 is {{WildFly Core}}. This results in the syslog server is not able to capture Process ID from which the message was sent.
> E.g. following piece of information is captured {{WildFly[Core] (...)}} instead of {{WildFlyCore[795]}}
> Suggestions for improvement:
> Change default value {{WildFly Core}} to one without space character.
> Also please consider addition of check whether {{app-name}} contains space character.
> [1] https://tools.ietf.org/html/rfc5424#page-8
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2048) ClassConfigurator: use constructors rather than Classes in map
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2048?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2048.
----------------------------
Resolution: Duplicate Issue
JGRP-2043 uses lambdas ({{Supplier<Header>}}) as values of the classMap hashmap. This is faster than storing {{MethodHandles}}.
> ClassConfigurator: use constructors rather than Classes in map
> --------------------------------------------------------------
>
> Key: JGRP-2048
> URL: https://issues.jboss.org/browse/JGRP-2048
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
>
> Investigate whether use of {{Constructor}} as values in the maps rather than {{Class<?>}} improves performance. {{Class.newInstance()}} does cache the constructor, but there's a security check that's executed once, so using the constructor may improve perf.
> Also, if a class doesn't have an empty constructor, using {{Class.newInstance()}} would throw an exception, whereas using constructors would detect this at load time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2048) ClassConfigurator: use constructors rather than Classes in map
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2048?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2048:
--------------------------------
Duplicate of JGRP-2043
> ClassConfigurator: use constructors rather than Classes in map
> --------------------------------------------------------------
>
> Key: JGRP-2048
> URL: https://issues.jboss.org/browse/JGRP-2048
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
>
> Investigate whether use of {{Constructor}} as values in the maps rather than {{Class<?>}} improves performance. {{Class.newInstance()}} does cache the constructor, but there's a security check that's executed once, so using the constructor may improve perf.
> Also, if a class doesn't have an empty constructor, using {{Class.newInstance()}} would throw an exception, whereas using constructors would detect this at load time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2042) Improve performance of Message#writeHeader
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2042?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2042.
----------------------------
Resolution: Done
> Improve performance of Message#writeHeader
> ------------------------------------------
>
> Key: JGRP-2042
> URL: https://issues.jboss.org/browse/JGRP-2042
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Sanne Grinovero
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
>
> The following stacktrace, taken with JFR, is highlighting a CPU consumer which could be optimised.
> {noformat}Stack Trace Sample Count Percentage(%)
> java.util.IdentityHashMap.get(Object) 66 2.224
> org.jgroups.conf.ClassConfigurator.getMagicNumber(Class) 66 2.224
> org.jgroups.Message.writeHeader(Header, DataOutput) 66 2.224
> {noformat}
> One idea could be to use an ad-hoc implementation of Map which takes advantage of the key being a {{Class}}. An interesting alternative would be to avoid the map lookup altogether, by having the Header expose a method like "writeMagicNumber(DataInput to)".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2042) Improve performance of Message#writeHeader
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2042?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2042:
--------------------------------
The solution picked was to add IDs to all {{Header}} subclasses and sanity check them against {{jg-magic-map.xml}}. When serializing a header instance, instead of getting the magic-ID via hashmap lookup, {{Header.getMagicId()}} is called instead. This avoids a hashmap lookup per header when serializaing a message. We have usually 3-4 headers per message, so 3-4 lookups per message we don't have to perform.
> Improve performance of Message#writeHeader
> ------------------------------------------
>
> Key: JGRP-2042
> URL: https://issues.jboss.org/browse/JGRP-2042
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Sanne Grinovero
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
>
> The following stacktrace, taken with JFR, is highlighting a CPU consumer which could be optimised.
> {noformat}Stack Trace Sample Count Percentage(%)
> java.util.IdentityHashMap.get(Object) 66 2.224
> org.jgroups.conf.ClassConfigurator.getMagicNumber(Class) 66 2.224
> org.jgroups.Message.writeHeader(Header, DataOutput) 66 2.224
> {noformat}
> One idea could be to use an ad-hoc implementation of Map which takes advantage of the key being a {{Class}}. An interesting alternative would be to avoid the map lookup altogether, by having the Header expose a method like "writeMagicNumber(DataInput to)".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months