[JBoss JIRA] (JGRP-2086) FD_SOCK is keep trying to create a new socket to the killed server
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2086?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2086:
--------------------------------
OK, these steps reproduce the issue:
* The view is \{A,B,C,D,E,F\}
* There's a network partition creating subclusters \{A,B,C\} and \{D,E,F\}
* As a result, the ABC side removes information about D,E,F from its cache ({{FD_SOCK.cache}}), and vice versa
* The partition heals and cluster \{A,B,C,D,E,F\} forms in a MergeView
* However, right after the merge, D, E and F crash
* C tries to get the IP address and port information about D (to connect to it), but because neither D nor E or F can provide this information, C remains in the endless loop, until FD_ALL kicks in
> FD_SOCK is keep trying to create a new socket to the killed server
> ------------------------------------------------------------------
>
> Key: JGRP-2086
> URL: https://issues.jboss.org/browse/JGRP-2086
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.3
> Environment: JDG 6.6.0 (jgroups-3.6.3.Final-redhat-4.jar)
> Reporter: Osamu Nagano
> Assignee: Bela Ban
> Fix For: 3.6.11, 4.0
>
>
> In most cases FD_SOCK can detect a killed server immediately. But for unknown reason, FD_SOCK is keep trying to create a new socket to the killed server. As a consequence, installing a new cluster view is delayed until FD_ALL is triggered.
> m04_n007_server.log is showing the behaviour. There is 28 nodes (4 machines (m03, ..., m06) and 7 nodes (n001, ..., n007) on each) and all nodes on m03 are killed at the same time on 15:07:34,543. FD_SOCK is keep trying to connect to a killed node saying "socket address for m03_n001/clustered could not be fetched, retrying".
> {noformat}
> [n007] 15:07:39,543 TRACE [org.jgroups.protocols.FD_SOCK] (Timer-8,shared=udp) m04_n007/clustered: broadcasting SUSPECT message (suspected_mbrs=[m03_n005/clustered, m03_n007/clustered])
> [n007] 15:07:39,544 TRACE [org.jgroups.protocols.FD_SOCK] (INT-20,shared=udp) m04_n007/clustered: received SUSPECT message from m04_n007/clustered: suspects=[m03_n005/clustered, m03_n007/clustered]
> [n007] 15:07:39,546 TRACE [org.jgroups.protocols.FD_SOCK] (FD_SOCK pinger,m04_n007/clustered) m04_n007/clustered: socket address for m03_n001/clustered could not be fetched, retrying
> [n007] 15:07:40,546 DEBUG [org.jgroups.protocols.FD_SOCK] (FD_SOCK pinger,m04_n007/clustered) m04_n007/clustered: ping_dest is m03_n001/clustered, pingable_mbrs=[m03_n001/clustered, m03_n002/clustered, m03_n003/clustered, m03_n004/clustered, m03_n006/clustered, m06_n001/clustered, m06_n002/clustered, m06_n003/clustered, m06_n004/clustered, m06_n005/clustered, m06_n006/clustered, m06_n007/clustered, m05_n001/clustered, m05_n002/clustered, m05_n003/clustered, m05_n004/clustered, m05_n005/clustered, m05_n006/clustered, m05_n007/clustered, m04_n001/clustered, m04_n002/clustered, m04_n003/clustered, m04_n004/clustered, m04_n005/clustered, m04_n006/clustered, m04_n007/clustered]
> [n007] 15:07:41,546 TRACE [org.jgroups.protocols.FD_SOCK] (FD_SOCK pinger,m04_n007/clustered) m04_n007/clustered: socket address for m03_n001/clustered could not be fetched, retrying
> [n007] 15:07:42,546 DEBUG [org.jgroups.protocols.FD_SOCK] (FD_SOCK pinger,m04_n007/clustered) m04_n007/clustered: ping_dest is m03_n001/clustered, pingable_mbrs=[m03_n001/clustered, m03_n002/clustered, m03_n003/clustered, m03_n004/clustered, m03_n006/clustered, m06_n001/clustered, m06_n002/clustered, m06_n003/clustered, m06_n004/clustered, m06_n005/clustered, m06_n006/clustered, m06_n007/clustered, m05_n001/clustered, m05_n002/clustered, m05_n003/clustered, m05_n004/clustered, m05_n005/clustered, m05_n006/clustered, m05_n007/clustered, m04_n001/clustered, m04_n002/clustered, m04_n003/clustered, m04_n004/clustered, m04_n005/clustered, m04_n006/clustered, m04_n007/clustered]
> [n007] 15:07:43,547 TRACE [org.jgroups.protocols.FD_SOCK] (FD_SOCK pinger,m04_n007/clustered) m04_n007/clustered: socket address for m03_n001/clustered could not be fetched, retrying
> ...
> [n007] 15:10:53,700 DEBUG [org.jgroups.protocols.FD_ALL] (Timer-26,shared=udp) haven't received a heartbeat from m03_n005/clustered for 200059 ms, adding it to suspect list
> {noformat}
> From the TRACE log, you can find an address cache of FD_SOCK has only 23 members.
> {noformat}
> [n007] 14:40:50,471 TRACE [org.jgroups.protocols.FD_SOCK] (FD_SOCK pinger,m04_n007/clustered) m04_n007/clustered: got cache from m03_n005/clustered: cache is {
> m04_n006/clustered=172.20.66.34:9945,
> m05_n005/clustered=172.20.66.35:9938,
> m06_n004/clustered=172.20.66.36:9931,
> m03_n007/clustered=172.20.66.33:9952,
> m05_n001/clustered=172.20.66.35:9910,
> m06_n005/clustered=172.20.66.36:9938,
> m05_n006/clustered=172.20.66.35:9945,
> m03_n005/clustered=172.20.66.33:9938,
> m05_n004/clustered=172.20.66.35:9931,
> m04_n003/clustered=172.20.66.34:9924,
> m04_n007/clustered=172.20.66.34:9952,
> m05_n002/clustered=172.20.66.35:9917,
> m05_n003/clustered=172.20.66.35:9924,
> m04_n004/clustered=172.20.66.34:9931,
> m06_n001/clustered=172.20.66.36:9910,
> m06_n007/clustered=172.20.66.36:9952,
> m04_n005/clustered=172.20.66.34:9938,
> m04_n001/clustered=172.20.66.34:9910,
> m05_n007/clustered=172.20.66.35:9952,
> m06_n002/clustered=172.20.66.36:9917,
> m06_n006/clustered=172.20.66.36:9945,
> m04_n002/clustered=172.20.66.34:9917,
> m06_n003/clustered=172.20.66.36:9924}
> {noformat}
> While pingable_mbrs has all 28 members which is from the current available cluster view.
> {noformat}
> [n007] 14:40:50,472 DEBUG [org.jgroups.protocols.FD_SOCK] (FD_SOCK pinger,m04_n007/clustered) m04_n007/clustered: ping_dest is m03_n005/clustered, pingable_mbrs=[
> m03_n005/clustered,
> m03_n007/clustered,
> m03_n001/clustered,
> m03_n002/clustered,
> m03_n003/clustered,
> m03_n004/clustered,
> m03_n006/clustered,
> m06_n001/clustered,
> m06_n002/clustered,
> m06_n003/clustered,
> m06_n004/clustered,
> m06_n005/clustered,
> m06_n006/clustered,
> m06_n007/clustered,
> m05_n001/clustered,
> m05_n002/clustered,
> m05_n003/clustered,
> m05_n004/clustered,
> m05_n005/clustered,
> m05_n006/clustered,
> m05_n007/clustered,
> m04_n001/clustered,
> m04_n002/clustered,
> m04_n003/clustered,
> m04_n004/clustered,
> m04_n005/clustered,
> m04_n006/clustered,
> m04_n007/clustered]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7133) Automatically define resource adapter for deployed RARs
by Guillermo González de Agüero (JIRA)
Guillermo González de Agüero created WFLY-7133:
--------------------------------------------------
Summary: Automatically define resource adapter for deployed RARs
Key: WFLY-7133
URL: https://issues.jboss.org/browse/WFLY-7133
Project: WildFly
Issue Type: Feature Request
Components: JCA
Affects Versions: 10.1.0.Final
Reporter: Guillermo González de Agüero
Assignee: Jesper Pedersen
Deploying a RAR file enables the resource adapter for the server, but in order to configure it, you must manually add it to the Resource Adapters subsystem. This is error prone (you can put in invalid "archive name" for the resource adapter and it doesn't complaint) and little user friendly.
>From a user perspective and from what can be read from the documentation (https://docs.jboss.org/author/display/WFLY10/Resource+adapters), it seems like the resource adapter is not enabled unless you explicitly define it.
It would be very simpler if RA deployments would be detected and registered as it's done for deployed JDBC drivers.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10.0.0.Final Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Summary: Wildfly 10.0.0.Final Messaging System issue (was: Wildfly 10.0.Final Messaging System issue)
> Wildfly 10.0.0.Final Messaging System issue
> -------------------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: standalone-full-WL-10.0.Final.xml, standalone-full-WL-8.2.xml, standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messages are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Issue Type: Component Upgrade (was: Bug)
> Wildfly 10.0.Final Messaging System issue
> -----------------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: standalone-full-WL-10.0.Final.xml, standalone-full-WL-8.2.xml, standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messages are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Priority: Critical (was: Blocker)
> Wildfly 10.0.Final Messaging System issue
> -----------------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: standalone-full-WL-10.0.Final.xml, standalone-full-WL-8.2.xml, standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messages are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-234) Inconsistent synchronization in ConfigurationFile
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-234?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-234:
------------------------------------
Fix Version/s: (was: 3.0.0.Alpha9)
> Inconsistent synchronization in ConfigurationFile
> -------------------------------------------------
>
> Key: WFCORE-234
> URL: https://issues.jboss.org/browse/WFCORE-234
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha11
> Reporter: Brian Stansberry
>
> ConfigurationFile synchronizes on itself in some places and not in others. This may cause problems, particularly with the history dir.
> The one that comes to mind is successfulBoot is synchronized, but all the methods called by ConfigurationFilePersistenceResource are not. The latter is called with the controller lock held, but the former is not. So there's a possibility of two threads interacting with the files concurrently if an operation executes immediately after boot.
> The deployment scanner schedules such an op, so it's possible. Currently the schedule is for 200 ms after deployment-scanner add runs during boot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-301) Configuration of individual contexts for http management interface.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-301?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-301:
-----------------------------------------
What is the status of this?
> Configuration of individual contexts for http management interface.
> -------------------------------------------------------------------
>
> Key: WFCORE-301
> URL: https://issues.jboss.org/browse/WFCORE-301
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: affects_elytron
> Fix For: 3.0.0.Alpha9
>
>
> At the moment all management requests are handled over the '/management' context, we also have a '/console' context to serve up the files for the admin console.
> The '/management' context is secured using standard HTTP mechanisms, this decision was taken so that clients could be written in different languages and all they would need to know is how to use standard authentication mechanisms. Due to problems where web browsers could run malicious scripts cross origin resource sharing is completely disabled for this context.
> We need to start to open up the handling of cross origin requests for a couple of reasons: -
> - Enabling Keycloak SSO support.
> - Alternative console distribution options
> The '/management' context is going to be retained as-is for legacy clients, possibly even switched off by default.
> A new context can then be added using non-browser based authentication, this could be SSO Keycloak or could be a form of Digest authentication where the response is handled by the console and not the web browser - either way as the browser is bypassed it is no longer at risk of sending malicious cross origin requests.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-13) End users can call non-published management API operations
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-13?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFCORE-13:
-----------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> End users can call non-published management API operations
> ----------------------------------------------------------
>
> Key: WFCORE-13
> URL: https://issues.jboss.org/browse/WFCORE-13
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Ladislav Thon
> Labels: EAP
> Fix For: 3.0.0.Alpha9
>
>
> It's not possible to call "non-published" operations (those that are not visible in the resource tree, e.g. {{describe}}) via JMX, while it's entirely possible to call them via CLI (e.g. {{/subsystem=security:describe}}) and other management interfaces.
> The problem lies in the fact that {{ModelControllerMBeanHelper.invoke}} method checks {{if (!accessControl.isExecutableOperation(operationName))}} and the {{isExecutableOperation}} method assumes that the operation will be visible in the resource tree. In fact, there is a comment stating _should not happen_, but now we know that it indeed _can_ happen.
> What's more, it gives a misleading error message. The {{isExecutableOperation}} returns {{false}} for unknown operations, which results in {{Not authorized to invoke operation}} message. Which is wrong in two different ways simultaneously: 1. the problem isn't authorization, but the fact that the operation can't be found; 2. the user (e.g. in the {{SuperUser}} role) _is_ authorized.
> I'm considering this low priority, because 1. JMX is likely to be very rarely used to access the management interface, 2. hiding information isn't nearly as important as leaking them, 3. non-published operations aren't nearly as important as the published ones. It's worth a JIRA nevertheless.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-301) Configuration of individual contexts for http management interface.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-301?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-301:
------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Configuration of individual contexts for http management interface.
> -------------------------------------------------------------------
>
> Key: WFCORE-301
> URL: https://issues.jboss.org/browse/WFCORE-301
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: affects_elytron
> Fix For: 3.0.0.Alpha9
>
>
> At the moment all management requests are handled over the '/management' context, we also have a '/console' context to serve up the files for the admin console.
> The '/management' context is secured using standard HTTP mechanisms, this decision was taken so that clients could be written in different languages and all they would need to know is how to use standard authentication mechanisms. Due to problems where web browsers could run malicious scripts cross origin resource sharing is completely disabled for this context.
> We need to start to open up the handling of cross origin requests for a couple of reasons: -
> - Enabling Keycloak SSO support.
> - Alternative console distribution options
> The '/management' context is going to be retained as-is for legacy clients, possibly even switched off by default.
> A new context can then be added using non-browser based authentication, this could be SSO Keycloak or could be a form of Digest authentication where the response is handled by the console and not the web browser - either way as the browser is bypassed it is no longer at risk of sending malicious cross origin requests.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-234) Inconsistent synchronization in ConfigurationFile
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-234?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-234:
------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Inconsistent synchronization in ConfigurationFile
> -------------------------------------------------
>
> Key: WFCORE-234
> URL: https://issues.jboss.org/browse/WFCORE-234
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha11
> Reporter: Brian Stansberry
> Fix For: 3.0.0.Alpha9
>
>
> ConfigurationFile synchronizes on itself in some places and not in others. This may cause problems, particularly with the history dir.
> The one that comes to mind is successfulBoot is synchronized, but all the methods called by ConfigurationFilePersistenceResource are not. The latter is called with the controller lock held, but the former is not. So there's a possibility of two threads interacting with the files concurrently if an operation executes immediately after boot.
> The deployment scanner schedules such an op, so it's possible. Currently the schedule is for 200 ms after deployment-scanner add runs during boot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-673) Elytron Integration with Core
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-673?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-673:
------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Elytron Integration with Core
> -----------------------------
>
> Key: WFCORE-673
> URL: https://issues.jboss.org/browse/WFCORE-673
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Alpha9
>
>
> This is the top level tracking task for Elytron integration within core. The tasks for the changes actually being made will either be linked or added as sub-tasks.
> In addition to this general issues that affect the Elytron integration are being labelled with 'affects_elytron' and can be queried using the following query: -
> https://issues.jboss.org/issues/?filter=12323574
> The label is a general catch-all for issues that are of interest to us but are not automatically blockers for our progress.
> The general criteria for the resolution of this issue will be: -
> - Inclusion of the Elytron Subsystem in core
> - All network entry points in core to be securable using Elytron
> - All SSL artefacts to be obtainable from Elytron.
> Note: The legacy modes will become better defined as we progress but whilst it must be possible to use Elytron it's use may still be optional to a certain degree.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-610) Integrate Elytron for management security.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-610?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-610:
------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Integrate Elytron for management security.
> ------------------------------------------
>
> Key: WFCORE-610
> URL: https://issues.jboss.org/browse/WFCORE-610
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 3.0.0.Alpha9
>
>
> This is a top level container task for the integration of Elytron for domain management security.
> Do note however that the purpose of Elytron is a single unified security solution across the whole of the application server so many tasks here will be groundwork for the remainder of the integration.
> At the moment the Elytron subsystem is being developed outside of wildfly-core, this will need to change in the future due to dependency issues (i.e. to write a subsystem you need to depend on core and core will need to include the subsystem (I think.)). However this will make it easier for now to ensure that the subsystem is 100% with no WildFly code accessing the subsystem - and also verify that we can create a distribtion with out the subsystem and still have a functional server.
> Overall if someone came up with an alternative subsystem that provided the same capabilities it should be possible to drop it in.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-363) ManagementResourceRegistration.getOverrideModel never returns null
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-363?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-363:
------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> ManagementResourceRegistration.getOverrideModel never returns null
> ------------------------------------------------------------------
>
> Key: WFCORE-363
> URL: https://issues.jboss.org/browse/WFCORE-363
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 3.0.0.Alpha9
>
>
> ManagementResourceRegistration.getOverrideModel ends up returning the wildcard registration if there is no override registration. This isn't correct.
> The fix isn't trivial because fixing it results in nasty failures in the smoke tests. From looking at the uses of this method (which all involve a null check) I assume there are some bugs in the code that calls this method that get exposed once it does what it should.
> This bug is the cause of the initial failure of my WFLY-2880 fix.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-311) Better error message if authentication is required to connect to the master but no realm is associated on the slave
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-311?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-311:
------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Better error message if authentication is required to connect to the master but no realm is associated on the slave
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-311
> URL: https://issues.jboss.org/browse/WFCORE-311
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Environment: RH EL 6.3 - JBoss EAP 6.2
> Reporter: Riccardo Benvenuti
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 3.0.0.Alpha9
>
>
> In JBoss 6.2 domain environment if in the host.xml file on the slave is missing the realm in the domain-controller tag as reported below
> <domain-controller>
> <remote host="10.123.137.200" port="9999"/>
> </domain-controller>
> we get the following error:
> JBoss Bootstrap Environment
> JBOSS_HOME: /opt/jboss7/jboss-eap-6.2
> JAVA: /usr/java/jdk1.7.0_51/bin/java
> JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:45:58,529 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
> 16:45:58,746 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 16:45:59,735 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
> [Host Controller] 16:45:59,913 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
> [Host Controller] 16:46:00,023 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting
> [Host Controller] 16:46:00,991 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1
> [Host Controller] 16:46:01,010 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
> [Host Controller] 16:46:01,033 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] 16:46:01,045 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.18.GA-redhat-1
> [Host Controller] 16:46:01,173 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 10.123.137.201:9999
> [Host Controller] 16:46:01,857 ERROR [org.jboss.remoting.remote.connection] (Remoting "testjb7s1:MANAGEMENT" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> [Host Controller] 16:46:01,869 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS010942: Unable to connect due to authentication failure.
> [Host Controller] 16:46:01,891 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> [Host Controller] JBAS014775: New missing/unsatisfied dependencies:
> [Host Controller] service jboss.server.controller.management.security_realm.ApplicationRealm.properties_authentication (missing) dependents: [service jboss.server.controller.management.security_realm.ApplicationRealm]
> [Host Controller]
> [Host Controller] 16:46:01,897 INFO [org.jboss.as.controller] (MSC service thread 1-1) JBAS014774: Service status report
> [Host Controller] JBAS014775: New missing/unsatisfied dependencies:
> [Host Controller] service jboss.server.controller.management.security_realm.ManagementRealm (missing) dependents: [service jboss.remoting.authentication_provider.management]
> [Host Controller]
> [Host Controller] 16:46:01,922 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> [Host Controller] JBAS014776: Newly corrected services:
> [Host Controller] service jboss.server.controller.management.security_realm.ApplicationRealm.properties_authentication (no longer required)
> [Host Controller] service jboss.server.controller.management.security_realm.ManagementRealm (no longer required)
> [Host Controller]
> [Host Controller] 16:46:01,927 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) stopped in 28ms
> 16:46:02,245 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 99
> 16:46:02,247 INFO [org.jboss.as.process] (Thread-8) JBAS012016: Shutting down process controller
> 16:46:02,247 INFO [org.jboss.as.process] (Thread-8) JBAS012015: All processes finished; exiting
> Adding the realm everything works correctly
> <domain-controller>
> <remote host="10.123.137.200" port="9999" security-realm="ManagementRealm"/>
> </domain-controller>
> Maybe a warning message could be useful to find the problem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1282) Unable to create HTTPS connection using *ECDH_RSA* cipher suites / kECDHr cipher string
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1282?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1282:
-------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Unable to create HTTPS connection using *ECDH_RSA* cipher suites / kECDHr cipher string
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-1282
> URL: https://issues.jboss.org/browse/WFCORE-1282
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 1.0.2.Final
> Environment: Oracle Java
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 3.0.0.Alpha9
>
> Attachments: client_debug_eap6.log, client_debug_eap7.log, server-cert-key-ec.jks, server_debug_eap6.log, server_debug_eap7.log
>
>
> User using these cipher suites / cipher name in EAP6 won't be able to use it in EAP7.
> Setting as critical as these cipher suites, are considered for strong and widely used in my opinion.
> In server log, error "no cipher suites in common" can be seen using -Djavax.net.debug=all.
> Note, that analogous configuration in EAP6 works fine.
> Issue can be seen on Oracle Java only, as on OpenJDK / IBM these suites are not provided by method getDefaultCipherSuites().
> Also is it possible to log "no cipher suites in common" and similar tls handshake errors without -Djavax.net.debug for better troubleshooting?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1145) Review of HostController / Application Server Remoting connections
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1145?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1145:
-------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Review of HostController / Application Server Remoting connections
> ------------------------------------------------------------------
>
> Key: WFCORE-1145
> URL: https://issues.jboss.org/browse/WFCORE-1145
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: affects_elytron
> Fix For: 3.0.0.Alpha9
>
>
> Where an application server connects back to it's host controller in domain mode it used the same Remoting connector exposed possibly for native domain management access.
> The problem with this is that as soon as any security restrictions are placed on the connector exposed by the host controller then the application servers require something to work with this - this is even though we are only ever talking about loopback communication between two process on the same machine.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1351) FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1351?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1351:
-------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager
> ------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1351
> URL: https://issues.jboss.org/browse/WFCORE-1351
> Project: WildFly Core
> Issue Type: Bug
> Components: Remoting, Security
> Reporter: Ondrej Kotek
> Assignee: David Lloyd
> Priority: Critical
> Fix For: 3.0.0.Alpha9
>
> Attachments: 1-no-createEndpoint-permission.stacktrace, 2-no-createXnioWorker-permission.stacktrace, 3-no-addConnectionProvider-permission.stacktrace, 4-no-accessDeclaredMembers-permission.stractrace, 5-no-suppressAccessChecks-permission.stracktrace
>
>
> # Running _NestedRemoteContextTestCase_ (from WildFly _testsuite/integration/basic_) with security manager, like
> {noformat}
> ./integration-tests.sh -Dts.basic -Dts.noSmoke -Dtest=NestedRemoteContextTestCase -Dsecurity.manager
> {noformat}
> results in exception:
> {noformat}
> java.io.IOException: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found
> {noformat}
> To make it work, permissions like following need to be added to _permissions.xml_ of _ejb.ear_:
> {noformat}
> new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/xnio/nio/main/*", "read"),
> new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/marshalling/river/main/*", "read"),
> new RemotingPermission("createEndpoint"),
> new RuntimePermission("createXnioWorker"),
> new RemotingPermission("addConnectionProvider"),
> new RuntimePermission("modifyThread"),
> new RuntimePermission("accessDeclaredMembers"),
> new ReflectPermission("suppressAccessChecks")
> {noformat}
> which is very confusing.
> Why do I need add seemingly unrelated permissions, like _FilePermission_ for XNIO and marshalling or _RuntimePermission_ for createXnioWorker? Such behavior should be fixed or properly documented.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1598) Conversion of Elytron SecurityIdentity to Subject for communication with older hosts.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1598?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1598:
-------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Conversion of Elytron SecurityIdentity to Subject for communication with older hosts.
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-1598
> URL: https://issues.jboss.org/browse/WFCORE-1598
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 3.0.0.Alpha9
>
>
> In the domain hierarchy clients trust the server they communicate with so this server currently sends a serialized representation of the Subject containing information about the user initiating the request.
> For Elytron we will use the new identity propagation features however for older slaves we will need to convert to a Subject representation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1533) Integrate Management Access Control permission assignment with Elytron
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1533?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1533:
-------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Integrate Management Access Control permission assignment with Elytron
> ----------------------------------------------------------------------
>
> Key: WFCORE-1533
> URL: https://issues.jboss.org/browse/WFCORE-1533
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: affects_elytron
> Fix For: 3.0.0.Alpha9
>
>
> A big portion of management role based access control is taking the assigned roles and then mapping these to the permissions for that role.
> Elytron provides a new PermissionMapper interface that takes a SecurityIdentity and the roles mapped for that identity and returns a PermissionVerifier which can be as simple as a wrapper around a PermissionCollection.
> This will also be a good opportunity to start to move the role mapping out of the core management model to Elytron.
> After that Elytron allows for custom PermissionMapper implementations to be provided and associated with the domain using capabilities and requirements so we arrive at a point where provided the permission checks performed by management are generic enough custom PermissionMapper / PermissionVerifier implementations can be added that may or may not be role based.
> _Note: As with everything we are doing old and new need to be supported in parallel for a while although this may be achieved by providing default Elytron implementations that are wrappers around the old._
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1701) In-VM Identity Representation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1701?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1701:
-------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> In-VM Identity Representation
> -----------------------------
>
> Key: WFCORE-1701
> URL: https://issues.jboss.org/browse/WFCORE-1701
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 3.0.0.Alpha9
>
>
> If Elytron has no current SecurityIdentity then an anonymous identity is used. The issue however is that this anonymous identity could be because the current user does not have access to be inflowed to the SecurityDomain being used for management or it could be because it is an in-vm call and no identity is established.
> We need a solution to safely represent an in-vm call and differentiate it from a user with no appropriate identity,
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1805) Intermittent failure in BasicOperationsUnitTestCase.testPathInfo
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1805?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1805:
-------------------------------------
Fix Version/s: 3.0.0.Alpha9
(was: 3.0.0.Alpha8)
> Intermittent failure in BasicOperationsUnitTestCase.testPathInfo
> ----------------------------------------------------------------
>
> Key: WFCORE-1805
> URL: https://issues.jboss.org/browse/WFCORE-1805
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Affects Versions: 3.0.0.Alpha7
> Reporter: Brian Stansberry
> Assignee: ehsavoie Hugonnet
> Fix For: 3.0.0.Alpha9
>
>
> This test is failing intermittently. I'm going to @Ignore it.
> This one should be a bit higher priority than the typical intermittent test failure as the stuff being tested is pretty new, so there's a higher chance this is a bug in the code instead of just a test issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla edited comment on WFLY-7131 at 9/16/16 3:56 PM:
-----------------------------------------------------------------
I have attached the standalone-full.xml for Wildfly 8.2 (which was working fine) as well as standalone-full.xml for Wildfly 10.0.Final (which is having this JMS related issue) for your reference
standalone-full-WL-8.2.xml is for Wildfly 8.2 which is working fine.
standalone-full-WL-10.0.Final.xml is for Wildfly 10.0.Final which has this JMS issue.
was (Author: kpreeta12):
The standalone-full.xml for Wildfly 10.0.0.Final is attached.
> Wildfly 10.0.Final Messaging System issue
> -----------------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full-WL-10.0.Final.xml, standalone-full-WL-8.2.xml, standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messages are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Description:
Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messages are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
<server name="default">
<security enabled="false"/>
<statistics enabled="true"/>
<security-setting name="#">
<role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
<role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
</security-setting>
<address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
<http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
<http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
<in-vm-connector name="in-vm" server-id="0"/>
<http-acceptor name="http-acceptor" http-listener="default"/>
<http-acceptor name="http-acceptor-throughput" http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver" value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
<jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
<jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
<jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
<jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
<jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
<jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
<jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
<pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
</server>
</subsystem>
was:
Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
<server name="default">
<security enabled="false"/>
<statistics enabled="true"/>
<security-setting name="#">
<role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
<role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
</security-setting>
<address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
<http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
<http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
<in-vm-connector name="in-vm" server-id="0"/>
<http-acceptor name="http-acceptor" http-listener="default"/>
<http-acceptor name="http-acceptor-throughput" http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver" value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
<jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
<jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
<jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
<jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
<jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
<jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
<jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
<pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
</server>
</subsystem>
> Wildfly 10.0.Final Messaging System issue
> -----------------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full-WL-10.0.Final.xml, standalone-full-WL-8.2.xml, standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messages are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla edited comment on WFLY-7131 at 9/16/16 3:51 PM:
-----------------------------------------------------------------
InitialContext is created with parameters - jmsuser, password, and
BEEERequisitions.JndiProviderUrl=http-remoting://<ip-address>:<port>
BEEERequisitions.JndiFactory=org.jboss.naming.remote.client.InitialContextFactory
Issue we face is that after we upgraded to wildfly 10, the messages are not going getting in the queues. This is not consistent as sometimes messages are getting processed.
Thanks,
Preeta
was (Author: kpreeta12):
InitialContext is created with parameters - jmsuser, password, and
BEEERequisitions.JndiProviderUrl=http-remoting://10.76.80.29:6080
BEEERequisitions.JndiFactory=org.jboss.naming.remote.client.InitialContextFactory
Issue we face is that after we upgraded to wildfly 10, the messages are not going getting in the queues. This is not consistent as sometimes messages are getting processed.
Thanks,
Preeta
> Wildfly 10.0.Final Messaging System issue
> -----------------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full-WL-10.0.Final.xml, standalone-full-WL-8.2.xml, standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Attachment: standalone-full-WL-8.2.xml
standalone-full-WL-10.0.Final.xml
I have attached the standalone-full.xml for Wildfly 8.2 (which was working fine) as well as standalone-full.xml for Wildfly 10.0.Final (which is having this JMS related issue) for your reference
> Wildfly 10.0.Final Messaging System issue
> -----------------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full-WL-10.0.Final.xml, standalone-full-WL-8.2.xml, standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Affects Version/s: 10.0.0.Final
(was: 8.2.0.Final)
> Wildfly 10.0.Final Messaging System issue
> -----------------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10.0.Final Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Summary: Wildfly 10.0.Final Messaging System issue (was: Wildfly 10 Messaging System issue)
> Wildfly 10.0.Final Messaging System issue
> -----------------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla edited comment on WFLY-7131 at 9/16/16 3:33 PM:
-----------------------------------------------------------------
InitialContext is created with parameters - jmsuser, password, and
BEEERequisitions.JndiProviderUrl=http-remoting://10.76.80.29:6080
BEEERequisitions.JndiFactory=org.jboss.naming.remote.client.InitialContextFactory
Issue we face is that after we upgraded to wildfly 10, the messages are not going getting in the queues. This is not consistent as sometimes messages are getting processed.
Thanks,
Preeta
was (Author: kpreeta12):
The above is used to create the InitialContext along with the other parameters - jmsuser, password, and
BEEERequisitions.JndiProviderUrl=http-remoting://10.76.80.29:6080
BEEERequisitions.JndiFactory=org.jboss.naming.remote.client.InitialContextFactory
Issue we face is that after we upgraded to wildfly 10, the messages are not going getting in the queues. This is not consistent as sometimes messages are getting processed.
Thanks,
Preeta
> Wildfly 10 Messaging System issue
> ---------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla edited comment on WFLY-7131 at 9/16/16 3:32 PM:
-----------------------------------------------------------------
The above is used to create the InitialContext along with the other parameters - jmsuser, password, and
BEEERequisitions.JndiProviderUrl=http-remoting://10.76.80.29:6080
BEEERequisitions.JndiFactory=org.jboss.naming.remote.client.InitialContextFactory
Issue we face is that after we upgraded to wildfly 10, the messages are not going getting in the queues. This is not consistent as sometimes messages are getting processed.
Thanks,
Preeta
was (Author: kpreeta12):
The client class that does the lookup for the JMS jndi does using the below
BEEERequisitions.JmsQueueFactory=jms/RemoteConnectionFactory
BEEERequisitions.JmsQueue=jms/queue/BEEERequisitionsQueue
BEEEAuthorizations.JmsQueueFactory=jms/RemoteConnectionFactory
BEEEAuthorizations.JmsQueue=jms/queue/BEEEAuthorizationsQueue
BEEEInbound.JmsQueueFactory=jms/RemoteConnectionFactory
BEEEInbound.JmsQueue=jms/queue/BEEEInboundQueue
ISEEOutbound.JmsQueueFactory=jms/RemoteConnectionFactory
ISEEOutbound.JmsQueue=jms/queue/ISEEOutboundQueue
The above is used to create the InitialContext along with the other parameters - jmsuser, password, and
BEEERequisitions.JndiProviderUrl=http-remoting://10.76.80.29:6080
BEEERequisitions.JndiFactory=org.jboss.naming.remote.client.InitialContextFactory
Let me know if you need any more info.
Issue we face is that after we upgraded to wildfly 10, the messages are not going getting received in the queues. This is not consistent as once in a while messages are getting processed.
Thanks,
Preeta
> Wildfly 10 Messaging System issue
> ---------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla commented on WFLY-7131:
----------------------------------------
The client class that does the lookup for the JMS jndi does using the below
BEEERequisitions.JmsQueueFactory=jms/RemoteConnectionFactory
BEEERequisitions.JmsQueue=jms/queue/BEEERequisitionsQueue
BEEEAuthorizations.JmsQueueFactory=jms/RemoteConnectionFactory
BEEEAuthorizations.JmsQueue=jms/queue/BEEEAuthorizationsQueue
BEEEInbound.JmsQueueFactory=jms/RemoteConnectionFactory
BEEEInbound.JmsQueue=jms/queue/BEEEInboundQueue
ISEEOutbound.JmsQueueFactory=jms/RemoteConnectionFactory
ISEEOutbound.JmsQueue=jms/queue/ISEEOutboundQueue
The above is used to create the InitialContext along with the other parameters - jmsuser, password, and
BEEERequisitions.JndiProviderUrl=http-remoting://10.76.80.29:6080
BEEERequisitions.JndiFactory=org.jboss.naming.remote.client.InitialContextFactory
Let me know if you need any more info.
Issue we face is that after we upgraded to wildfly 10, the messages are not going getting received in the queues. This is not consistent as once in a while messages are getting processed.
Thanks,
Preeta
> Wildfly 10 Messaging System issue
> ---------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Attachment: standalone-full.xml
The standalone-full.xml for Wildfly 10.0.0.Final is attached.
> Wildfly 10 Messaging System issue
> ---------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: standalone-full.xml
>
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Description:
Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
<server name="default">
<security enabled="false"/>
<statistics enabled="true"/>
<security-setting name="#">
<role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
<role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
</security-setting>
<address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
<http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
<http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
<in-vm-connector name="in-vm" server-id="0"/>
<http-acceptor name="http-acceptor" http-listener="default"/>
<http-acceptor name="http-acceptor-throughput" http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver" value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
<jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
<jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
<jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
<jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
<jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
<jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
<jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
<pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
</server>
</subsystem>
was:
Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
Basically the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
Let me know if this is good. Also I am attaching the entire standalone-full.xml
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
<server name="default" persistence-enabled="false">
<security enabled="false"/>
<statistics enabled="true"/>
<security-setting name="#">
<role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
<role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
</security-setting>
<address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
<http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
<http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
<in-vm-connector name="in-vm" server-id="0"/>
<http-acceptor name="http-acceptor" http-listener="default"/>
<http-acceptor name="http-acceptor-throughput" http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver" value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
<jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
<jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
<jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
<jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
<jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
<jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
<jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
<pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
</server>
</subsystem>
> Wildfly 10 Messaging System issue
> ---------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> The issue we are facing is after we upgraded our application to wildfly 10.0.0.Final from Wildfly 8.2 the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml with this case.
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-7131?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-7131:
-----------------------------------
Description:
Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
Basically the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
Let me know if this is good. Also I am attaching the entire standalone-full.xml
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
<server name="default" persistence-enabled="false">
<security enabled="false"/>
<statistics enabled="true"/>
<security-setting name="#">
<role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
<role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
</security-setting>
<address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
<http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
<http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
<in-vm-connector name="in-vm" server-id="0"/>
<http-acceptor name="http-acceptor" http-listener="default"/>
<http-acceptor name="http-acceptor-throughput" http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver" value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
<jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
<jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
<jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
<jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
<jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
<jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
<jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
<pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
</server>
</subsystem>
was:
Following are the testing scenarios we did and the outcome:-
1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment.
2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment.
3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment
4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment.
Jgroups subsystem configuration in domain.xml we have is below:-
<subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp">
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE2"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
</subsystem>
> Wildfly 10 Messaging System issue
> ---------------------------------
>
> Key: WFLY-7131
> URL: https://issues.jboss.org/browse/WFLY-7131
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Widlffly 8.2 was based on HornetQ JMS message broker while Wildfly 10 uses ActiveMQ JMS message broker.
> The HornetQ code base was donated to the Apache ActiveMQ community late last year and now resides as a sub project under the ActiveMQ umbrella named 'Artemis’. http://activemq.apache.org/artemis.
> http://hornetq.blogspot.in/2015/06/hornetq-apache-donation-and-apache.html
> Basically the messaging are not consistently getting into the queue. Below is how we configured the messaging subsystem in standalone-full.xml:-
> Let me know if this is good. Also I am attaching the entire standalone-full.xml
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
> <server name="default" persistence-enabled="false">
> <security enabled="false"/>
> <statistics enabled="true"/>
> <security-setting name="#">
> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> <role name="jmsrole" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/>
> </security-setting>
> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/>
> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="remote-http"/>
> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"/>
> <in-vm-connector name="in-vm" server-id="0"/>
> <http-acceptor name="http-acceptor" http-listener="default"/>
> <http-acceptor name="http-acceptor-throughput" http-listener="default">
> <param name="batch-delay" value="50"/>
> <param name="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> <jms-queue name="testQueue" entries="queue/test jboss/exported/jms/queue/test"/>
> <jms-queue name="ISEEOutboundQueue" entries="/ISEEOutboundQueue java:jboss/exported/jms/queue/ISEEOutboundQueue"/>
> <jms-queue name="ISEEInboundQueue" entries="/ISEEInboundQueue java:jboss/exported/jms/queue/ISEEInboundQueue"/>
> <jms-queue name="BEEEAuthorizationsQueue" entries="/BEEEAuthorizationsQueue java:jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
> <jms-queue name="BEEERequisitionsQueue" entries="/BEEERequisitionsQueue java:jboss/exported/jms/queue/BEEERequisitionsQueue"/>
> <jms-queue name="BEEEInboundQueue" entries="/BEEEInboundQueue java:jboss/exported/jms/queue/BEEEInboundQueue"/>
> <jms-topic name="testTopic" entries="topic/test java:jboss/exported/jms/topic/test"/>
> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory /RemoteConnectionFactory" connectors="http-connector"/>
> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/>
> </server>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7129) Removing XA Datasources via CLI OR DMR does not de-register it from the context without reload.
by shailendra singh (JIRA)
[ https://issues.jboss.org/browse/WFLY-7129?page=com.atlassian.jira.plugin.... ]
shailendra singh edited comment on WFLY-7129 at 9/16/16 2:51 PM:
-----------------------------------------------------------------
possible fix
https://github.com/wildfly/wildfly/pull/9198
was (Author: rhn-support-shsingh):
possible fix
https://issues.jboss.org/browse/WFLY-7129
> Removing XA Datasources via CLI OR DMR does not de-register it from the context without reload.
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-7129
> URL: https://issues.jboss.org/browse/WFLY-7129
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 10.1.0.Final
> Reporter: shailendra singh
> Assignee: Brian Stansberry
> Priority: Minor
>
> Below is the result of add .. remove ..add operation of XADatasource .
> 1. Add - OK
> {code:java}
> [domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:add(jndi-name=java\:jboss\/datasources\/oracleXaDatasource,driver-name=oracle-driver.jar)
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> {code}
> 2. Remove - OK
> {code:java}
> [domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:remove()
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> {code}
> 3. Add - Error is thrown
> {code:java}
> [domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:add(jndi-name=java\:jboss\/datasources\/oracleXaDatasource,driver-name=oracle-driver.jar)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.data-source.TestXADataSource' is already registered in context 'profile=default'."},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7131) Wildfly 10 Messaging System issue
by Preeta Kuruvilla (JIRA)
Preeta Kuruvilla created WFLY-7131:
--------------------------------------
Summary: Wildfly 10 Messaging System issue
Key: WFLY-7131
URL: https://issues.jboss.org/browse/WFLY-7131
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 8.2.0.Final
Reporter: Preeta Kuruvilla
Assignee: Jeff Mesnil
Priority: Blocker
Following are the testing scenarios we did and the outcome:-
1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment.
2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment.
3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment
4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment.
Jgroups subsystem configuration in domain.xml we have is below:-
<subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp">
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE2"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
</subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1805) Intermittent failure in BasicOperationsUnitTestCase.testPathInfo
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1805:
----------------------------------------
Summary: Intermittent failure in BasicOperationsUnitTestCase.testPathInfo
Key: WFCORE-1805
URL: https://issues.jboss.org/browse/WFCORE-1805
Project: WildFly Core
Issue Type: Bug
Components: Domain Management, Test Suite
Affects Versions: 3.0.0.Alpha7
Reporter: Brian Stansberry
Assignee: ehsavoie Hugonnet
Fix For: 3.0.0.Alpha8
This test is failing intermittently. I'm going to @Ignore it.
This one should be a bit higher priority than the typical intermittent test failure as the stuff being tested is pretty new, so there's a higher chance this is a bug in the code instead of just a test issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7075) proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped or to check if unsync context is already joined to JTA TX
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-7075?page=com.atlassian.jira.plugin.... ]
Scott Marlow edited comment on WFLY-7075 at 9/16/16 2:31 PM:
-------------------------------------------------------------
Any feedback on three recent commits on [https://github.com/scottmarlow/wildfly/tree/WFLY-7075_unsyncXPCExtension]?
[https://github.com/scottmarlow/wildfly/commit/4d3ec0eb2b9ce4034191afa41a8...] addresses https://issues.jboss.org/browse/WFLY-7130 to allow properties to be passed into the @PersistenceContext so users can choose to use either of the two extension hints for the injected persistence context.
[https://github.com/scottmarlow/wildfly/commit/b78c5ae9f1712672480451ce477...] adds the two extension hints for https://issues.jboss.org/browse/WFLY-7075 "wildfly.jpa.allowjoinedunsync=true" can be specified at the @PersistenceContext level to allow a joined UNSYNCHRONIZED pc to be used. "wildfly.jpa.skipmixedsynctypechecking=true" can be specified at the @PersistenceContext level to disable the checking for mixed sync/unsync persistence contexts. We also also allow the same hints to be specified in the persistence.xml as well.
[https://github.com/scottmarlow/wildfly/commit/df62fbbb0583b1834583c8cac29...] addresses the reported defect (now via WFLY-7108), that ExtendedEntityManager.getSynchronizationType() should return the synchronizationType, instead of SynchronizationType.SYNCHRONIZED.
was (Author: smarlow):
Any feedback on three recent commits on [https://github.com/scottmarlow/wildfly/tree/WFLY-7075_unsyncXPCExtension]?
[https://github.com/scottmarlow/wildfly/commit/f137b958d03278b0f67bb30391b...] addresses https://issues.jboss.org/browse/WFLY-7130 to allow properties to be passed into the @PersistenceContext so users can choose to use either of the two extension hints for the injected persistence context.
[https://github.com/scottmarlow/wildfly/commit/484f05a83394a9ba941d12d4a1e...] adds the two extension hints for https://issues.jboss.org/browse/WFLY-7075 "wildfly.jpa.allowjoinedunsync=true" can be specified at the @PersistenceContext level to allow a joined UNSYNCHRONIZED pc to be used. "wildfly.jpa.skipmixedsynctypechecking=true" can be specified at the @PersistenceContext level to disable the checking for mixed sync/unsync persistence contexts. We also also allow the same hints to be specified in the persistence.xml as well.
[https://github.com/scottmarlow/wildfly/commit/df62fbbb0583b1834583c8cac29...] addresses the reported defect (now via WFLY-7108), that ExtendedEntityManager.getSynchronizationType() should return the synchronizationType, instead of SynchronizationType.SYNCHRONIZED.
> proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped or to check if unsync context is already joined to JTA TX
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7075
> URL: https://issues.jboss.org/browse/WFLY-7075
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: *AppServer:* WildFly 10.1.0.Final
> *WildFly-jpa:* wildfly-jpa-10.1.0.Final.jar
> Reporter: Viacheslav Astapkovich
> Assignee: Scott Marlow
> Attachments: kitchensink-ear.rar
>
>
> As we mentioned in https://issues.jboss.org/browse/WFLY-6127 we found bug and made our solution.
>
> *The obtained defect:*
> A defect related to the check of synchronization type (to satisfy JPA spec 2.1 section 7.6.4.1) was found in WildFly 10.1.0.Final.
> The Method getSynchronizationType of class ExtendedEntityManager ALWAYS returns type of synchronization as SYNCHRONIZED (jar file: wildfly-jpa-10.1.0.Final.jar)
> *FIX:*
> We made a fork of WildFly-jpa project at: https://github.com/argustelecom/wildfly/tree/WFLY-6127
> Our Fix commit: https://github.com/wildfly/wildfly/commit/3bff5fde3cfc23f3999dc75c320029e...
> _Changes_: The method getSynchronizationType returns declared synchronization type.
> [WFLY-7108] is now the tracking jira for the fix.
> *Consequences:*
> We use own realisation of Martin Fowler pattern "Unit of Work". We initialize UNSYNCHRONIZED Extended Persistence Context and our UnitOfWork realisation manages the synchronization with transaction.
> Our Beans could be controlled by UnitOfWork, but also could be used as part of WebService call.
> It requires a declaration of synchronize persistence context.
> We catch IllegalStateException after we fixed defect of synchronization type determination, because we initialize UNSYNCHRONIZED persistence context, but we use declare SYNCHRONIZED persistence context in our beans.
> However, our UnitOfWork realisation control synchronization of persistence context and we can synchronize context before synchronization type check.
> *Our actions:*
> We add ability to check synchronization type in the method testForMixedSynchronizationTypes of class TransactionScopedEntityManager by isJoinToTransaction method (i.e. the actual type of synchronization).
> This ability realized by property "jboss.as.jpa.syncasjoin" in persistence.xml file. Only if this property setted to true - we perform testForMixedSynchronizationTypes by isJoinToTransaction method. We work as usual if this property not defined or setted to false.
> _Commit_: https://github.com/wildfly/wildfly/commit/195a8a65a9fae006ad603e425f6a16d...
> *Example for reproduction:*
> I modified quickstart example: [^kitchensink-ear.rar]
> MemberRepository begin Extended UNSYNCHRONIZED Persistence Context.
> MemberFinder.find called from MemberRepository. MemberFinder declared "SYNCHRONIZED", but MemberRepository declared UNSYNCHRONIZED.
> MemberRepository also perform join Transaction.
> Questions from [~smarlow]:
> - whether you could instead use an application-managed entity manager instead (which is similar to extended persistence context except the app controls it.
> We decided to use Container-managed EntityManager, because
> - Application-managed entity managers don’t automatically propagate the JTA transaction context. With application-managed entity managers the persistence context is not propagated to application components
> - The container makes our job
> We want to use the existing mechanism
> *In Addition:*
> Formally, this is out of JPA SPEC, but we have the following reasons:
> - In the development process of the JPA specification got a question: "Should we relax this if the PC has been joined to the transaction?".
> But unfortunately, Linda DeMichiel decided to leave as current behavior because no feedback was given.
> ( https://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2011-08/m... )
> - We found JIRA task https://java.net/jira/browse/JPA_SPEC-6 but it was closed because "No feedback in favor of changing current approach"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7075) proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped or to check if unsync context is already joined to JTA TX
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-7075?page=com.atlassian.jira.plugin.... ]
Scott Marlow edited comment on WFLY-7075 at 9/16/16 2:27 PM:
-------------------------------------------------------------
Any feedback on three recent commits on [https://github.com/scottmarlow/wildfly/tree/WFLY-7075_unsyncXPCExtension]?
[https://github.com/scottmarlow/wildfly/commit/f137b958d03278b0f67bb30391b...] addresses https://issues.jboss.org/browse/WFLY-7130 to allow properties to be passed into the @PersistenceContext so users can choose to use either of the two extension hints for the injected persistence context.
[https://github.com/scottmarlow/wildfly/commit/484f05a83394a9ba941d12d4a1e...] adds the two extension hints for https://issues.jboss.org/browse/WFLY-7075 "wildfly.jpa.allowjoinedunsync=true" can be specified at the @PersistenceContext level to allow a joined UNSYNCHRONIZED pc to be used. "wildfly.jpa.skipmixedsynctypechecking=true" can be specified at the @PersistenceContext level to disable the checking for mixed sync/unsync persistence contexts. We also also allow the same hints to be specified in the persistence.xml as well.
[https://github.com/scottmarlow/wildfly/commit/df62fbbb0583b1834583c8cac29...] addresses the reported defect (now via WFLY-7108), that ExtendedEntityManager.getSynchronizationType() should return the synchronizationType, instead of SynchronizationType.SYNCHRONIZED.
was (Author: smarlow):
Any feedback on three recent commits on [https://github.com/scottmarlow/wildfly/tree/WFLY-7075_unsyncXPCExtension]?
[https://github.com/scottmarlow/wildfly/commit/f137b958d03278b0f67bb30391b...] addresses https://issues.jboss.org/browse/WFLY-7130 to allow properties to be passed into the @PersistenceContext so users can choose to use either of the two extension hints for the injected persistence context.
[https://github.com/scottmarlow/wildfly/commit/484f05a83394a9ba941d12d4a1e...] adds the two extension hints for https://issues.jboss.org/browse/WFLY-7075 "wildfly.jpa.allowjoinedunsync=true" can be specified at the @PersistenceContext level to allow a joined UNSYNCHRONIZED pc to be used. "wildfly.jpa.skipmixedsynctypechecking=true" can be specified at the @PersistenceContext level to disable the checking for mixed sync/unsync persistence contexts. It might be better to also allow the hints to be specified in the persistence.xml as well.
[https://github.com/scottmarlow/wildfly/commit/df62fbbb0583b1834583c8cac29...] addresses the reported defect (now via WFLY-7108), that ExtendedEntityManager.getSynchronizationType() should return the synchronizationType, instead of SynchronizationType.SYNCHRONIZED.
> proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped or to check if unsync context is already joined to JTA TX
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7075
> URL: https://issues.jboss.org/browse/WFLY-7075
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: *AppServer:* WildFly 10.1.0.Final
> *WildFly-jpa:* wildfly-jpa-10.1.0.Final.jar
> Reporter: Viacheslav Astapkovich
> Assignee: Scott Marlow
> Attachments: kitchensink-ear.rar
>
>
> As we mentioned in https://issues.jboss.org/browse/WFLY-6127 we found bug and made our solution.
>
> *The obtained defect:*
> A defect related to the check of synchronization type (to satisfy JPA spec 2.1 section 7.6.4.1) was found in WildFly 10.1.0.Final.
> The Method getSynchronizationType of class ExtendedEntityManager ALWAYS returns type of synchronization as SYNCHRONIZED (jar file: wildfly-jpa-10.1.0.Final.jar)
> *FIX:*
> We made a fork of WildFly-jpa project at: https://github.com/argustelecom/wildfly/tree/WFLY-6127
> Our Fix commit: https://github.com/wildfly/wildfly/commit/3bff5fde3cfc23f3999dc75c320029e...
> _Changes_: The method getSynchronizationType returns declared synchronization type.
> [WFLY-7108] is now the tracking jira for the fix.
> *Consequences:*
> We use own realisation of Martin Fowler pattern "Unit of Work". We initialize UNSYNCHRONIZED Extended Persistence Context and our UnitOfWork realisation manages the synchronization with transaction.
> Our Beans could be controlled by UnitOfWork, but also could be used as part of WebService call.
> It requires a declaration of synchronize persistence context.
> We catch IllegalStateException after we fixed defect of synchronization type determination, because we initialize UNSYNCHRONIZED persistence context, but we use declare SYNCHRONIZED persistence context in our beans.
> However, our UnitOfWork realisation control synchronization of persistence context and we can synchronize context before synchronization type check.
> *Our actions:*
> We add ability to check synchronization type in the method testForMixedSynchronizationTypes of class TransactionScopedEntityManager by isJoinToTransaction method (i.e. the actual type of synchronization).
> This ability realized by property "jboss.as.jpa.syncasjoin" in persistence.xml file. Only if this property setted to true - we perform testForMixedSynchronizationTypes by isJoinToTransaction method. We work as usual if this property not defined or setted to false.
> _Commit_: https://github.com/wildfly/wildfly/commit/195a8a65a9fae006ad603e425f6a16d...
> *Example for reproduction:*
> I modified quickstart example: [^kitchensink-ear.rar]
> MemberRepository begin Extended UNSYNCHRONIZED Persistence Context.
> MemberFinder.find called from MemberRepository. MemberFinder declared "SYNCHRONIZED", but MemberRepository declared UNSYNCHRONIZED.
> MemberRepository also perform join Transaction.
> Questions from [~smarlow]:
> - whether you could instead use an application-managed entity manager instead (which is similar to extended persistence context except the app controls it.
> We decided to use Container-managed EntityManager, because
> - Application-managed entity managers don’t automatically propagate the JTA transaction context. With application-managed entity managers the persistence context is not propagated to application components
> - The container makes our job
> We want to use the existing mechanism
> *In Addition:*
> Formally, this is out of JPA SPEC, but we have the following reasons:
> - In the development process of the JPA specification got a question: "Should we relax this if the PC has been joined to the transaction?".
> But unfortunately, Linda DeMichiel decided to leave as current behavior because no feedback was given.
> ( https://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2011-08/m... )
> - We found JIRA task https://java.net/jira/browse/JPA_SPEC-6 but it was closed because "No feedback in favor of changing current approach"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7129) Removing XA Datasources via CLI OR DMR does not de-register it from the context without reload.
by shailendra singh (JIRA)
[ https://issues.jboss.org/browse/WFLY-7129?page=com.atlassian.jira.plugin.... ]
shailendra singh commented on WFLY-7129:
----------------------------------------
possible fix
https://issues.jboss.org/browse/WFLY-7129
> Removing XA Datasources via CLI OR DMR does not de-register it from the context without reload.
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-7129
> URL: https://issues.jboss.org/browse/WFLY-7129
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 10.1.0.Final
> Reporter: shailendra singh
> Assignee: Brian Stansberry
> Priority: Minor
>
> Below is the result of add .. remove ..add operation of XADatasource .
> 1. Add - OK
> {code:java}
> [domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:add(jndi-name=java\:jboss\/datasources\/oracleXaDatasource,driver-name=oracle-driver.jar)
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> {code}
> 2. Remove - OK
> {code:java}
> [domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:remove()
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> {code}
> 3. Add - Error is thrown
> {code:java}
> [domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:add(jndi-name=java\:jboss\/datasources\/oracleXaDatasource,driver-name=oracle-driver.jar)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.data-source.TestXADataSource' is already registered in context 'profile=default'."},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7075) proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped or to check if unsync context is already joined to JTA TX
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-7075?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-7075:
------------------------------------
Any feedback on three recent commits on [https://github.com/scottmarlow/wildfly/tree/WFLY-7075_unsyncXPCExtension]?
[https://github.com/scottmarlow/wildfly/commit/f137b958d03278b0f67bb30391b...] addresses https://issues.jboss.org/browse/WFLY-7130 to allow properties to be passed into the @PersistenceContext so users can choose to use either of the two extension hints for the injected persistence context.
[https://github.com/scottmarlow/wildfly/commit/484f05a83394a9ba941d12d4a1e...] adds the two extension hints for https://issues.jboss.org/browse/WFLY-7075 "wildfly.jpa.allowjoinedunsync=true" can be specified at the @PersistenceContext level to allow a joined UNSYNCHRONIZED pc to be used. "wildfly.jpa.skipmixedsynctypechecking=true" can be specified at the @PersistenceContext level to disable the checking for mixed sync/unsync persistence contexts. It might be better to also allow the hints to be specified in the persistence.xml as well.
[https://github.com/scottmarlow/wildfly/commit/df62fbbb0583b1834583c8cac29...] addresses the reported defect (now via WFLY-7108), that ExtendedEntityManager.getSynchronizationType() should return the synchronizationType, instead of SynchronizationType.SYNCHRONIZED.
> proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped or to check if unsync context is already joined to JTA TX
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7075
> URL: https://issues.jboss.org/browse/WFLY-7075
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: *AppServer:* WildFly 10.1.0.Final
> *WildFly-jpa:* wildfly-jpa-10.1.0.Final.jar
> Reporter: Viacheslav Astapkovich
> Assignee: Scott Marlow
> Attachments: kitchensink-ear.rar
>
>
> As we mentioned in https://issues.jboss.org/browse/WFLY-6127 we found bug and made our solution.
>
> *The obtained defect:*
> A defect related to the check of synchronization type (to satisfy JPA spec 2.1 section 7.6.4.1) was found in WildFly 10.1.0.Final.
> The Method getSynchronizationType of class ExtendedEntityManager ALWAYS returns type of synchronization as SYNCHRONIZED (jar file: wildfly-jpa-10.1.0.Final.jar)
> *FIX:*
> We made a fork of WildFly-jpa project at: https://github.com/argustelecom/wildfly/tree/WFLY-6127
> Our Fix commit: https://github.com/wildfly/wildfly/commit/3bff5fde3cfc23f3999dc75c320029e...
> _Changes_: The method getSynchronizationType returns declared synchronization type.
> [WFLY-7108] is now the tracking jira for the fix.
> *Consequences:*
> We use own realisation of Martin Fowler pattern "Unit of Work". We initialize UNSYNCHRONIZED Extended Persistence Context and our UnitOfWork realisation manages the synchronization with transaction.
> Our Beans could be controlled by UnitOfWork, but also could be used as part of WebService call.
> It requires a declaration of synchronize persistence context.
> We catch IllegalStateException after we fixed defect of synchronization type determination, because we initialize UNSYNCHRONIZED persistence context, but we use declare SYNCHRONIZED persistence context in our beans.
> However, our UnitOfWork realisation control synchronization of persistence context and we can synchronize context before synchronization type check.
> *Our actions:*
> We add ability to check synchronization type in the method testForMixedSynchronizationTypes of class TransactionScopedEntityManager by isJoinToTransaction method (i.e. the actual type of synchronization).
> This ability realized by property "jboss.as.jpa.syncasjoin" in persistence.xml file. Only if this property setted to true - we perform testForMixedSynchronizationTypes by isJoinToTransaction method. We work as usual if this property not defined or setted to false.
> _Commit_: https://github.com/wildfly/wildfly/commit/195a8a65a9fae006ad603e425f6a16d...
> *Example for reproduction:*
> I modified quickstart example: [^kitchensink-ear.rar]
> MemberRepository begin Extended UNSYNCHRONIZED Persistence Context.
> MemberFinder.find called from MemberRepository. MemberFinder declared "SYNCHRONIZED", but MemberRepository declared UNSYNCHRONIZED.
> MemberRepository also perform join Transaction.
> Questions from [~smarlow]:
> - whether you could instead use an application-managed entity manager instead (which is similar to extended persistence context except the app controls it.
> We decided to use Container-managed EntityManager, because
> - Application-managed entity managers don’t automatically propagate the JTA transaction context. With application-managed entity managers the persistence context is not propagated to application components
> - The container makes our job
> We want to use the existing mechanism
> *In Addition:*
> Formally, this is out of JPA SPEC, but we have the following reasons:
> - In the development process of the JPA specification got a question: "Should we relax this if the PC has been joined to the transaction?".
> But unfortunately, Linda DeMichiel decided to leave as current behavior because no feedback was given.
> ( https://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2011-08/m... )
> - We found JIRA task https://java.net/jira/browse/JPA_SPEC-6 but it was closed because "No feedback in favor of changing current approach"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7075) proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped or to check if unsync context is already joined to JTA TX
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-7075?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-7075:
-------------------------------
Summary: proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped or to check if unsync context is already joined to JTA TX (was: proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped)
> proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped or to check if unsync context is already joined to JTA TX
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7075
> URL: https://issues.jboss.org/browse/WFLY-7075
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: *AppServer:* WildFly 10.1.0.Final
> *WildFly-jpa:* wildfly-jpa-10.1.0.Final.jar
> Reporter: Viacheslav Astapkovich
> Assignee: Scott Marlow
> Attachments: kitchensink-ear.rar
>
>
> As we mentioned in https://issues.jboss.org/browse/WFLY-6127 we found bug and made our solution.
>
> *The obtained defect:*
> A defect related to the check of synchronization type (to satisfy JPA spec 2.1 section 7.6.4.1) was found in WildFly 10.1.0.Final.
> The Method getSynchronizationType of class ExtendedEntityManager ALWAYS returns type of synchronization as SYNCHRONIZED (jar file: wildfly-jpa-10.1.0.Final.jar)
> *FIX:*
> We made a fork of WildFly-jpa project at: https://github.com/argustelecom/wildfly/tree/WFLY-6127
> Our Fix commit: https://github.com/wildfly/wildfly/commit/3bff5fde3cfc23f3999dc75c320029e...
> _Changes_: The method getSynchronizationType returns declared synchronization type.
> [WFLY-7108] is now the tracking jira for the fix.
> *Consequences:*
> We use own realisation of Martin Fowler pattern "Unit of Work". We initialize UNSYNCHRONIZED Extended Persistence Context and our UnitOfWork realisation manages the synchronization with transaction.
> Our Beans could be controlled by UnitOfWork, but also could be used as part of WebService call.
> It requires a declaration of synchronize persistence context.
> We catch IllegalStateException after we fixed defect of synchronization type determination, because we initialize UNSYNCHRONIZED persistence context, but we use declare SYNCHRONIZED persistence context in our beans.
> However, our UnitOfWork realisation control synchronization of persistence context and we can synchronize context before synchronization type check.
> *Our actions:*
> We add ability to check synchronization type in the method testForMixedSynchronizationTypes of class TransactionScopedEntityManager by isJoinToTransaction method (i.e. the actual type of synchronization).
> This ability realized by property "jboss.as.jpa.syncasjoin" in persistence.xml file. Only if this property setted to true - we perform testForMixedSynchronizationTypes by isJoinToTransaction method. We work as usual if this property not defined or setted to false.
> _Commit_: https://github.com/wildfly/wildfly/commit/195a8a65a9fae006ad603e425f6a16d...
> *Example for reproduction:*
> I modified quickstart example: [^kitchensink-ear.rar]
> MemberRepository begin Extended UNSYNCHRONIZED Persistence Context.
> MemberFinder.find called from MemberRepository. MemberFinder declared "SYNCHRONIZED", but MemberRepository declared UNSYNCHRONIZED.
> MemberRepository also perform join Transaction.
> Questions from [~smarlow]:
> - whether you could instead use an application-managed entity manager instead (which is similar to extended persistence context except the app controls it.
> We decided to use Container-managed EntityManager, because
> - Application-managed entity managers don’t automatically propagate the JTA transaction context. With application-managed entity managers the persistence context is not propagated to application components
> - The container makes our job
> We want to use the existing mechanism
> *In Addition:*
> Formally, this is out of JPA SPEC, but we have the following reasons:
> - In the development process of the JPA specification got a question: "Should we relax this if the PC has been joined to the transaction?".
> But unfortunately, Linda DeMichiel decided to leave as current behavior because no feedback was given.
> ( https://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2011-08/m... )
> - We found JIRA task https://java.net/jira/browse/JPA_SPEC-6 but it was closed because "No feedback in favor of changing current approach"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7130) PersistenceProperty specified in @PersistenceContext should be passed to the created EntityManager
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-7130?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-7130:
-------------------------------
Component/s: JPA / Hibernate
> PersistenceProperty specified in @PersistenceContext should be passed to the created EntityManager
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-7130
> URL: https://issues.jboss.org/browse/WFLY-7130
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: JBoss AS7 7.1.1.Final, 10.1.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
>
> While working on the unit test for WFLY-7075, I noticed that PersistenceContext properties are not being passed correctly to the Injected EntityManager, we should fix that.
> For Example:
> {quote}
> @PersistenceContext(type = PersistenceContextType.TRANSACTION, unitName = "mypc", properties={@PersistenceProperty(name="wildfly.jpa.allowjoinedunsync", value="true")})
> private EntityManager allowjoinedunsyncEm;
> {quote}
> Is passing an incorrect form of the property values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7130) PersistenceProperty specified in @PersistenceContext should be passed to the created EntityManager
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-7130?page=com.atlassian.jira.plugin.... ]
Scott Marlow reassigned WFLY-7130:
----------------------------------
Assignee: Scott Marlow (was: Jason Greene)
> PersistenceProperty specified in @PersistenceContext should be passed to the created EntityManager
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-7130
> URL: https://issues.jboss.org/browse/WFLY-7130
> Project: WildFly
> Issue Type: Bug
> Affects Versions: JBoss AS7 7.1.1.Final, 10.1.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
>
> While working on the unit test for WFLY-7075, I noticed that PersistenceContext properties are not being passed correctly to the Injected EntityManager, we should fix that.
> For Example:
> {quote}
> @PersistenceContext(type = PersistenceContextType.TRANSACTION, unitName = "mypc", properties={@PersistenceProperty(name="wildfly.jpa.allowjoinedunsync", value="true")})
> private EntityManager allowjoinedunsyncEm;
> {quote}
> Is passing an incorrect form of the property values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBAS-9584) (1.8.0.0(.7.8.4 6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/JBAS-9584?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar deleted JBAS-9584:
------------------------------
> (1.8.0.0(.7.8.4 6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-9584
> URL: https://issues.jboss.org/browse/JBAS-9584
> Project: Application Server 3 4 5 and 6
> Issue Type: Feature Request
> Environment: (1.8.0.0(.7.8.4 6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> Reporter: jira mira
>
> (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> @ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 Meri Mehbooba @ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 usaHow @@cow hp printer support phone number 1 800 784 6124 hp printer support phone number usa How @@@@how 1 800 784 6124 Hp printer support phone number@@@!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA&&&!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA Testing 1 800 784 6124 Hp printer support phone number hp printer phone number status @PrinTer .1-800-784-6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa $$$$ CALL%%%%%!!!!!!!!Hp Printer tech Support Number @1-800-784-6124@ Hp Printer Tech Support Phone Number Call wireless 1-800-784-6124 1-800- 784-6124 Hp Tech Support Phone Number Canada Hp printer customer service number1-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, hewlett packard support, Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, hewlett packard customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, hewlett packard printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, hewlett packard phone number, Hp printer customer service, Hp printer tech support number, Hp product support, hewlett packard customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support, hewlett packard tech support, Hp online chat, hewlett packard technical support, Hp printer help line, phone number for Hp support, hewlett packard support phone number, Hp printer technical support, hewlett packard customer service number, Hp service number, hewlett packard helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1800 number, Hp support phone, Hp support line, hewlett packard contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, hewlett packard support number, hewlett packard tech support number, Hp support telephone number, hewlett packard tech support phone number, call Hp, Hp contact support, hewlett packard technical support phone number, Hp support centre, hewlett packard customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, hewlett packard help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact hewlett packard by phone, Hp printer phone support, hewlett packard printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, hewlett packard customer service telephone number, phone number for hewlett packard, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, hewlett packard customer service phone, Hp laptop tech support, Hp service phone number, hewlett packard printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 800 number, hewlett packard technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact hewlett packard, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, hewlett packard telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, hewlett packard contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, hewlett packard printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, hewlett packard help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, hewlett packard support center, Hp laptop customer care no, Hp printer support telephone number, Hp support 1 800 247 1987 services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, hewlett packard customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, hewlett packard printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for hewlett packard customer service, hewlett packard 800 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 800 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, hewlett packard computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, contact Hp laptop support, Hp customer service contact number, support for Hp printer, Hp printer customer care no, 1 800 247 1987 Hp computer phone number, Hp tech help, Hp pc support number, Hp laptop customer support, Hp desktop support number, support Hp printer, Hp support hours, number for Hp support, Hp support customer service number, Hp contact phone number, customer service number for Hp printers, Hp computers help, Hp tech support contact number, Hp phone support Tech vew sUpP0RT.... Hp @PrinTer .1-800-7846124- .Support Phone Number,HP printer tech support number, HP Printer Customer Care Phone Number uSa. $UPP0RT.... Hp @PrinTer .1-800-784-6124- .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa. HppRintERTEchSuppORtphOnENumbER1-800-784-6124HppRintERSuppORtphOnENumbER,HppRintERSuppORtNumbER,HppRintERtEchSuppORtNumbER..HppRintERssuppORtphOnEnumbER”-HppRintERsphOnEnumbER) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada Hp pRintER tEch suppORt phOnE numbER usa!!+++++1-800-784-6124+++Hp pRintER tEch suppORt phOnE numbER usa...pDF, Hp pRintER 1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,Hp pRintER tEchnical suppORt numbER1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,cannOn pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER,Hp 1-800-784-6124Hp pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER 1-800-784-6124 Hp pRINTER tEch suppORt phOnE numbER USA !!Call aus 1-800-784-6124Hp TEch SuppORt phOnE NumbER UK-800-784-6124 Hp suppORt numbER, Hp suppORt, Hp pRintER suppORt, Hp tEch suppORt, Hp tEchnical suppORt, Hp custOmER sERvicE numbER, Hp custOmER sERvicE, Hp tEch suppORt numbER, Hp suppORt cEntER, Hp pRintER suppORt numbER, Hp suppORt suppORt, 1-800-784-6124 Hp cOntact numbER, Hp phOnE numbER, Hp hElp and suppORt, Hp custOmER suppORt, Hp pRintER hElp, Hp tEchnical suppORt numbER, Hp suppORt phOnE numbER, Hp suppORt custOmER sERvicE, Hp pRintERs suppORt, Hp custOmER sERvicE phOnE numbER, Hp numbER, Hp custOmER caRE, Hp cOntact, Hp tEch suppORt phOnE numbER, Hp suppORt chat, Hp custOmER suppORt numbER, Hp custOmER caRE numbER, cOntact Hp suppORt, Hp hElp, Hp phOnE, Hp pRintER suppORt phOnE numbER, Hp custOmER suppORt phOnE numbER, Hp pRintER tEch suppORt, Hp phOnE suppORt, Hp tEchnical suppORt phOnE numbER, Hp laptOp suppORt numbER, Hp suppORt pRintER suppORt, Hp hElplinE, Hp tElEphOnE suppORt, Hp OnlinE suppORt, Hp suppORt cOntact, Hp chat suppORt, Hp suppORt phOnE numbER, Hp pRintER custOmER sERvicE, Hp pRintER tEch suppORt numbER, Hp pROduct suppORt 1-800-784-6124 , Hp suppORt custOmER sERvicE phOnE numbER, Hp cOmputER suppORt numbER, Hp suppORt cOntact numbER, Hp suppORt pRintER, Hp cOmputER suppORt, Hp tEch suppORt chat, Hp hElplinE numbER, Hp laptOp suppORt1-800-784-6124, Hp suppORt tEch suppORt, Hp OnlinE chat, Hp suppORt tEchnical suppORt, Hp pRintER hElp linE, phOnE numbER fOR Hp suppORt, Hp suppORt suppORt phOnE numbER 1-800-784-6124, Hp pRintER tEchnical suppORt, Hp suppORt custOmER sERvicE numbER, Hp sERvicE numbER, Hp suppORt hElplinE, Hp custOmER caRE nO, Hp pRintER custOmER sERvicE numbER, Hp hElp numbER, Hp pRintER custOmER sERvicE phOnE numbER, Hp 1-800-784-6124 numbER, Hp suppORt phOnE, Hp suppORt linE, Hp suppORt cOntact numbER, Hp pRintER tEch suppORt phOnE numbER, Hp pRintER custOmER suppORt phOnE numbER, Hp pRintERs hElp, call Hp suppORt, Hp pRintER suppORt chat, Hp suppORt suppORt numbER, Hp suppORt tEch suppORt numbER, Hp suppORt tElEphOnE numbER, Hp suppORt tEch suppORt phOnE numbER, call Hp, Hp cOntact suppORt, Hp suppORt tEchnical suppORt phOnE numbER, Hp suppORt cEntRE, Hp suppORt custOmER suppORt, Hp dEsktOp suppORt, Hp laptOp custOmER sERvicE, cOntact Hp pRintER suppORt, Hp pc suppORt, Hp laptOp custOmER caRE numbER, Hp suppORt fOR pRintERs, Hp pRintER custOmER caRE, Hp custOmER caRE phOnE numbER, Hp suppORt hElp, phOnE numbER fOR Hp, Hp OnlinE hElp, Hp laptOp custOmER caRE, Hp hElplinE phOnE numbER, Hp pRintER custOmER suppORt, Hp tEchnical suppORt chat, Hp cOmputER hElp, Hp suppORt numbERs, Hp tEchnical suppORt cOntact numbER, Hp tElEphOnE numbER, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER hElplinE, Hp suppORt pRintERs1-800-784-6124, Hp suppORt OnlinE, Hp pRintER cOntact numbER, Hp hElp phOnE numbER, Hp pRintER custOmER caRE numbER, cOntact Hp suppORt by phOnE, Hp pRintER phOnE suppORt, Hp suppORt pRintERs suppORt, Hp tEch suppORt phOnE, Hp tEchnical hElp, Hp laptOp tEch suppORt numbER, cOntact Hp by phOnE, Hp suppORt call, Hp cOmputERs suppORt, Hp suppORt custOmER sERvicE tElEphOnE numbER, phOnE numbER fOR Hp suppORt, Hp OnlinE suppORt chat, Hp laptOp custOmER sERvicE numbER, Hp OnlinE chat suppORt, Hp pRintERs custOmER sERvicE, Hp suppORt custOmER sERvicE phOnE, Hp laptOp tEch suppORt, Hp sERvicE phOnE numbER, Hp suppORt pRintER hElp, phOnE numbER fOR Hp pRintERs, Hp tROublEshOOting phOnE numbER, Hp 1-800-784-6124numbER, Hp suppORt tEchnical suppORt numbER, cOntact Hp suppORt phOnE, phOnE numbER fOR Hp pRintER suppORt, Hp custOmER suppORt chat, Hp hElp and suppORt numbER, cOntact Hp suppORt, Hp laptOp suppORt phOnE numbER, Hp pRintERs custOmER sERvicE phOnE numbER, Hp laptOp custOmER sERvicE phOnE numbER, Hp cOmputER suppORt phOnE numbER, Hp paviliOn suppORt, Hp cOmputER custOmER sERvicE, Hp custOmER sERvicEs, Hp suppORt tElEphOnE numbER, Hp hElplinE nO, Hp hElp dEsk numbER, cOntact Hp suppORt phOnE numbER, Hp suppORt cOntact, Hp phOnE numbERs, Hp pRintERs custOmER caRE numbER, Hp pRintER hElp and suppORt, cOntact Hp tEchnical suppORt, Hp cOntact numbERs, cOntact Hp suppORt chat, call Hp tEch suppORt, Hp custOmER sERvicE phOnE, Hp hElp suppORt, Hp cOmputER tEch suppORt, Hp assistancE phOnE numbER, Hp custOmER sERvicE tElEphOnE numbER, Hp suppORt pRintER suppORt phOnE numbER, Hp cOntact suppORt numbER, Hp suppORt cEntER phOnE numbER, Hp suppORt phOnE numbERs, tEch suppORt fOR Hp, Hp it suppORt, Hp laptOp hElplinE, Hp tEchnical, Hp laptOp tEchnical suppORt numbER, Hp pRintERs tEch suppORt phOnE numbER, Hp pRintERs suppORt phOnE numbER, Hp suppORt hElp dEsk phOnE numbER, Hp cOmputER tEch suppORt phOnE numbER, Hp custOmER sERvicE numbER fOR laptOp, Hp pRintER hElplinE numbER, cOntact Hp suppORt by phOnE, Hp suppORt suppORt cEntER, Hp laptOp custOmER caRE nO, Hp pRintER suppORt tElEphOnE numbER, Hp suppORt sERvicEs, Hp custOmER sERvicE numbER fOR pRintERs, Hp pROduct suppORt numbER, Hp laptOp tEch suppORt phOnE numbER, Hp pRintER hElplinE phOnE numbER, cOntact Hp custOmER suppORt, Hp suppORt custOmER suppORt phOnE numbER, Hp pRintERs tEchnical suppORt, Hp custOmER caRE cEntER, suppORt fOR Hp pRintERs, Hp pRintER suppORt cEntER, phOnE numbER fOR Hp tEch suppORt, Hp dEsktOp custOmER caRE numbER, Hp laptOps suppORt, Hp pRintER OnlinE suppORt, Hp pRintER phOnE numbER, Hp suppORt pRintERs suppORt phOnE numbER, tEchnical suppORt fOR Hp pRintERs phOnE numbER, Hp hElp cEntER phOnE numbER, cOntact Hp tEch suppORt, call Hp pRintER suppORt, Hp pRintERs custOmER suppORt, Hp cOmputER custOmER sERvicE numbER, Hp pRintERs hElplinE, Hp custOmER caRE cOntact numbER, Hp laptOp hElp, Hp cOmputER custOmER sERvicE phOnE numbER, phOnE numbER fOR Hp suppORt custOmER sERvicE, Hp suppORt 1-800-784-6124 numbER, Hp pRintER hElp phOnE numbER, Hp pRintERs hElp phOnE numbER, Hp pRintER phOnE numbER fOR custOmER sERvicE, Hp cOmputER tEchnical suppORt phOnE numbER, custOmER sERvicE Hp, Hp suppORt tEchnical suppORt numbER, cOntact numbER fOR Hp, Hp cOmputERs suppORt phOnE numbER, Hp pRintERs suppORt numbER, Hp pRintER tEchnical suppORt numbER, cOntact Hp tEch suppORt by phOnE, Hp cOmputER custOmER caRE numbER, Hp pRintER 1-800-784-6124 numbER, call Hp custOmER sERvicE, Hp pRintER hElp cEntER, Hp cOmputERs custOmER sERvicE, Hp pRintER hElp dEsk, Hp suppORt cOmputER suppORt, Hp pRintERs tEchnical suppORt numbER, Hp hElp dEsk phOnE numbER, Hp pRintER suppORt phOnE, Hp cOntact hElp, cOntact Hp laptOp suppORt, Hp custOmER sERvicE cOntact numbER, suppORt fOR Hp pRintER, Hp pRintER custOmER caRE nO, Hp cOmputER phOnE numbER, Hp tEch hElp, Hp pc suppORt numbER, Hp laptOp custOmER suppORt, Hp dEsktOp suppORt numbER, suppORt Hp pRintER, Hp suppORt hOuRs, numbER fOR Hp suppORt, Hp suppORt custOmER sERvicE numbER, Hp cOntact phOnE numbER, custOmER sERvicE numbER fOR Hp pRintERs, Hp cOmputERs hElp, Hp tEch suppORt cOntact numbER, Hp phOnE suppORt numbER Most Urgent 1 800 784 6124 Hp printer support phone number hp printer customer care phone number HpPRinterTechSupportPhoneNumber1-800-784 6124HpPrinterSupportPhoneNumber,HpPrinterSupportNumber,HpPrintertechSupportNumber..HpPrinterssupportphonenumber”-HpPrintersphonenumber) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada Hp printer tech support phone number usa!!+++++1-800-784-6124+++Hp printer tech support phone number usa...PDF, Hp printer 1-800-784-6124 Hp printer customer service phone number,Hp printer technical support number1-800-784-6124 Hp printer customer service phone number,cannon printer helpline, Hp printer technical support phone number, Hp printer tech support number,Hp 1-800-784-6124Hp printer helpline, Hp printer technical support phone number, Hp printer tech support number 1-800-784-6124 Hp PRINTER tech support phone number USA !!Call aus 1-800-784-6124Hp Tech Support Phone Number UK-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, Hp support support, 1-800-784-6124 Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, Hp support customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, Hp support printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, Hp support phone number, Hp printer customer service, Hp printer tech support number, Hp product support 1-800-784-6124 , Hp support customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support1-800-784-6124, Hp support tech support, Hp online chat, Hp support technical support, Hp printer help line, phone number for Hp support, Hp support support phone number 1-800-784-6124, Hp printer technical support, Hp support customer service number, Hp service number, Hp support helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1-800-784-6124 number, Hp support phone, Hp support line, Hp support contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, Hp support support number, Hp support tech support number, Hp support telephone number, Hp support tech support phone number, call Hp, Hp contact support, Hp support technical support phone number, Hp support centre, Hp support customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, Hp support help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers1-800-784-6124, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact Hp support by phone, Hp printer phone support, Hp support printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, Hp support customer service telephone number, phone number for Hp support, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, Hp support customer service phone, Hp laptop tech support, Hp service phone number, Hp support printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 1-800-784-6124number, Hp support technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact Hp support, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, Hp support telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, Hp support contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, Hp support printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, Hp support help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, Hp support support center, Hp laptop customer care no, Hp printer support telephone number, Hp support services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, Hp support customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, Hp support printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for Hp support customer service, Hp support 1-800-784-6124 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 1-800-784-6124 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, Hp support computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ • EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHON
> Files
> Filter
> NameModified
> (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBAS-9583) (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/JBAS-9583?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar deleted JBAS-9583:
------------------------------
> (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> --------------------------------------------------------------------------------------------------------
>
> Key: JBAS-9583
> URL: https://issues.jboss.org/browse/JBAS-9583
> Project: Application Server 3 4 5 and 6
> Issue Type: Feature Request
> Environment: (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> Reporter: jira mira
>
> (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT
> @ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 Meri Mehbooba @ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 usaHow @@cow hp printer support phone number 1 800 784 6124 hp printer support phone number usa How @@@@how 1 800 784 6124 Hp printer support phone number@@@!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA&&&!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA Testing 1 800 784 6124 Hp printer support phone number hp printer phone number status @PrinTer .1-800-784-6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa $$$$ CALL%%%%%!!!!!!!!Hp Printer tech Support Number @1-800-784-6124@ Hp Printer Tech Support Phone Number Call wireless 1-800-784-6124 1-800- 784-6124 Hp Tech Support Phone Number Canada Hp printer customer service number1-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, hewlett packard support, Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, hewlett packard customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, hewlett packard printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, hewlett packard phone number, Hp printer customer service, Hp printer tech support number, Hp product support, hewlett packard customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support, hewlett packard tech support, Hp online chat, hewlett packard technical support, Hp printer help line, phone number for Hp support, hewlett packard support phone number, Hp printer technical support, hewlett packard customer service number, Hp service number, hewlett packard helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1800 number, Hp support phone, Hp support line, hewlett packard contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, hewlett packard support number, hewlett packard tech support number, Hp support telephone number, hewlett packard tech support phone number, call Hp, Hp contact support, hewlett packard technical support phone number, Hp support centre, hewlett packard customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, hewlett packard help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact hewlett packard by phone, Hp printer phone support, hewlett packard printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, hewlett packard customer service telephone number, phone number for hewlett packard, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, hewlett packard customer service phone, Hp laptop tech support, Hp service phone number, hewlett packard printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 800 number, hewlett packard technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact hewlett packard, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, hewlett packard telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, hewlett packard contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, hewlett packard printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, hewlett packard help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, hewlett packard support center, Hp laptop customer care no, Hp printer support telephone number, Hp support 1 800 247 1987 services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, hewlett packard customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, hewlett packard printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for hewlett packard customer service, hewlett packard 800 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 800 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, hewlett packard computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, contact Hp laptop support, Hp customer service contact number, support for Hp printer, Hp printer customer care no, 1 800 247 1987 Hp computer phone number, Hp tech help, Hp pc support number, Hp laptop customer support, Hp desktop support number, support Hp printer, Hp support hours, number for Hp support, Hp support customer service number, Hp contact phone number, customer service number for Hp printers, Hp computers help, Hp tech support contact number, Hp phone support Tech vew sUpP0RT.... Hp @PrinTer .1-800-7846124- .Support Phone Number,HP printer tech support number, HP Printer Customer Care Phone Number uSa. $UPP0RT.... Hp @PrinTer .1-800-784-6124- .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa. HppRintERTEchSuppORtphOnENumbER1-800-784-6124HppRintERSuppORtphOnENumbER,HppRintERSuppORtNumbER,HppRintERtEchSuppORtNumbER..HppRintERssuppORtphOnEnumbER”-HppRintERsphOnEnumbER) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada Hp pRintER tEch suppORt phOnE numbER usa!!+++++1-800-784-6124+++Hp pRintER tEch suppORt phOnE numbER usa...pDF, Hp pRintER 1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,Hp pRintER tEchnical suppORt numbER1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,cannOn pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER,Hp 1-800-784-6124Hp pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER 1-800-784-6124 Hp pRINTER tEch suppORt phOnE numbER USA !!Call aus 1-800-784-6124Hp TEch SuppORt phOnE NumbER UK-800-784-6124 Hp suppORt numbER, Hp suppORt, Hp pRintER suppORt, Hp tEch suppORt, Hp tEchnical suppORt, Hp custOmER sERvicE numbER, Hp custOmER sERvicE, Hp tEch suppORt numbER, Hp suppORt cEntER, Hp pRintER suppORt numbER, Hp suppORt suppORt, 1-800-784-6124 Hp cOntact numbER, Hp phOnE numbER, Hp hElp and suppORt, Hp custOmER suppORt, Hp pRintER hElp, Hp tEchnical suppORt numbER, Hp suppORt phOnE numbER, Hp suppORt custOmER sERvicE, Hp pRintERs suppORt, Hp custOmER sERvicE phOnE numbER, Hp numbER, Hp custOmER caRE, Hp cOntact, Hp tEch suppORt phOnE numbER, Hp suppORt chat, Hp custOmER suppORt numbER, Hp custOmER caRE numbER, cOntact Hp suppORt, Hp hElp, Hp phOnE, Hp pRintER suppORt phOnE numbER, Hp custOmER suppORt phOnE numbER, Hp pRintER tEch suppORt, Hp phOnE suppORt, Hp tEchnical suppORt phOnE numbER, Hp laptOp suppORt numbER, Hp suppORt pRintER suppORt, Hp hElplinE, Hp tElEphOnE suppORt, Hp OnlinE suppORt, Hp suppORt cOntact, Hp chat suppORt, Hp suppORt phOnE numbER, Hp pRintER custOmER sERvicE, Hp pRintER tEch suppORt numbER, Hp pROduct suppORt 1-800-784-6124 , Hp suppORt custOmER sERvicE phOnE numbER, Hp cOmputER suppORt numbER, Hp suppORt cOntact numbER, Hp suppORt pRintER, Hp cOmputER suppORt, Hp tEch suppORt chat, Hp hElplinE numbER, Hp laptOp suppORt1-800-784-6124, Hp suppORt tEch suppORt, Hp OnlinE chat, Hp suppORt tEchnical suppORt, Hp pRintER hElp linE, phOnE numbER fOR Hp suppORt, Hp suppORt suppORt phOnE numbER 1-800-784-6124, Hp pRintER tEchnical suppORt, Hp suppORt custOmER sERvicE numbER, Hp sERvicE numbER, Hp suppORt hElplinE, Hp custOmER caRE nO, Hp pRintER custOmER sERvicE numbER, Hp hElp numbER, Hp pRintER custOmER sERvicE phOnE numbER, Hp 1-800-784-6124 numbER, Hp suppORt phOnE, Hp suppORt linE, Hp suppORt cOntact numbER, Hp pRintER tEch suppORt phOnE numbER, Hp pRintER custOmER suppORt phOnE numbER, Hp pRintERs hElp, call Hp suppORt, Hp pRintER suppORt chat, Hp suppORt suppORt numbER, Hp suppORt tEch suppORt numbER, Hp suppORt tElEphOnE numbER, Hp suppORt tEch suppORt phOnE numbER, call Hp, Hp cOntact suppORt, Hp suppORt tEchnical suppORt phOnE numbER, Hp suppORt cEntRE, Hp suppORt custOmER suppORt, Hp dEsktOp suppORt, Hp laptOp custOmER sERvicE, cOntact Hp pRintER suppORt, Hp pc suppORt, Hp laptOp custOmER caRE numbER, Hp suppORt fOR pRintERs, Hp pRintER custOmER caRE, Hp custOmER caRE phOnE numbER, Hp suppORt hElp, phOnE numbER fOR Hp, Hp OnlinE hElp, Hp laptOp custOmER caRE, Hp hElplinE phOnE numbER, Hp pRintER custOmER suppORt, Hp tEchnical suppORt chat, Hp cOmputER hElp, Hp suppORt numbERs, Hp tEchnical suppORt cOntact numbER, Hp tElEphOnE numbER, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER hElplinE, Hp suppORt pRintERs1-800-784-6124, Hp suppORt OnlinE, Hp pRintER cOntact numbER, Hp hElp phOnE numbER, Hp pRintER custOmER caRE numbER, cOntact Hp suppORt by phOnE, Hp pRintER phOnE suppORt, Hp suppORt pRintERs suppORt, Hp tEch suppORt phOnE, Hp tEchnical hElp, Hp laptOp tEch suppORt numbER, cOntact Hp by phOnE, Hp suppORt call, Hp cOmputERs suppORt, Hp suppORt custOmER sERvicE tElEphOnE numbER, phOnE numbER fOR Hp suppORt, Hp OnlinE suppORt chat, Hp laptOp custOmER sERvicE numbER, Hp OnlinE chat suppORt, Hp pRintERs custOmER sERvicE, Hp suppORt custOmER sERvicE phOnE, Hp laptOp tEch suppORt, Hp sERvicE phOnE numbER, Hp suppORt pRintER hElp, phOnE numbER fOR Hp pRintERs, Hp tROublEshOOting phOnE numbER, Hp 1-800-784-6124numbER, Hp suppORt tEchnical suppORt numbER, cOntact Hp suppORt phOnE, phOnE numbER fOR Hp pRintER suppORt, Hp custOmER suppORt chat, Hp hElp and suppORt numbER, cOntact Hp suppORt, Hp laptOp suppORt phOnE numbER, Hp pRintERs custOmER sERvicE phOnE numbER, Hp laptOp custOmER sERvicE phOnE numbER, Hp cOmputER suppORt phOnE numbER, Hp paviliOn suppORt, Hp cOmputER custOmER sERvicE, Hp custOmER sERvicEs, Hp suppORt tElEphOnE numbER, Hp hElplinE nO, Hp hElp dEsk numbER, cOntact Hp suppORt phOnE numbER, Hp suppORt cOntact, Hp phOnE numbERs, Hp pRintERs custOmER caRE numbER, Hp pRintER hElp and suppORt, cOntact Hp tEchnical suppORt, Hp cOntact numbERs, cOntact Hp suppORt chat, call Hp tEch suppORt, Hp custOmER sERvicE phOnE, Hp hElp suppORt, Hp cOmputER tEch suppORt, Hp assistancE phOnE numbER, Hp custOmER sERvicE tElEphOnE numbER, Hp suppORt pRintER suppORt phOnE numbER, Hp cOntact suppORt numbER, Hp suppORt cEntER phOnE numbER, Hp suppORt phOnE numbERs, tEch suppORt fOR Hp, Hp it suppORt, Hp laptOp hElplinE, Hp tEchnical, Hp laptOp tEchnical suppORt numbER, Hp pRintERs tEch suppORt phOnE numbER, Hp pRintERs suppORt phOnE numbER, Hp suppORt hElp dEsk phOnE numbER, Hp cOmputER tEch suppORt phOnE numbER, Hp custOmER sERvicE numbER fOR laptOp, Hp pRintER hElplinE numbER, cOntact Hp suppORt by phOnE, Hp suppORt suppORt cEntER, Hp laptOp custOmER caRE nO, Hp pRintER suppORt tElEphOnE numbER, Hp suppORt sERvicEs, Hp custOmER sERvicE numbER fOR pRintERs, Hp pROduct suppORt numbER, Hp laptOp tEch suppORt phOnE numbER, Hp pRintER hElplinE phOnE numbER, cOntact Hp custOmER suppORt, Hp suppORt custOmER suppORt phOnE numbER, Hp pRintERs tEchnical suppORt, Hp custOmER caRE cEntER, suppORt fOR Hp pRintERs, Hp pRintER suppORt cEntER, phOnE numbER fOR Hp tEch suppORt, Hp dEsktOp custOmER caRE numbER, Hp laptOps suppORt, Hp pRintER OnlinE suppORt, Hp pRintER phOnE numbER, Hp suppORt pRintERs suppORt phOnE numbER, tEchnical suppORt fOR Hp pRintERs phOnE numbER, Hp hElp cEntER phOnE numbER, cOntact Hp tEch suppORt, call Hp pRintER suppORt, Hp pRintERs custOmER suppORt, Hp cOmputER custOmER sERvicE numbER, Hp pRintERs hElplinE, Hp custOmER caRE cOntact numbER, Hp laptOp hElp, Hp cOmputER custOmER sERvicE phOnE numbER, phOnE numbER fOR Hp suppORt custOmER sERvicE, Hp suppORt 1-800-784-6124 numbER, Hp pRintER hElp phOnE numbER, Hp pRintERs hElp phOnE numbER, Hp pRintER phOnE numbER fOR custOmER sERvicE, Hp cOmputER tEchnical suppORt phOnE numbER, custOmER sERvicE Hp, Hp suppORt tEchnical suppORt numbER, cOntact numbER fOR Hp, Hp cOmputERs suppORt phOnE numbER, Hp pRintERs suppORt numbER, Hp pRintER tEchnical suppORt numbER, cOntact Hp tEch suppORt by phOnE, Hp cOmputER custOmER caRE numbER, Hp pRintER 1-800-784-6124 numbER, call Hp custOmER sERvicE, Hp pRintER hElp cEntER, Hp cOmputERs custOmER sERvicE, Hp pRintER hElp dEsk, Hp suppORt cOmputER suppORt, Hp pRintERs tEchnical suppORt numbER, Hp hElp dEsk phOnE numbER, Hp pRintER suppORt phOnE, Hp cOntact hElp, cOntact Hp laptOp suppORt, Hp custOmER sERvicE cOntact numbER, suppORt fOR Hp pRintER, Hp pRintER custOmER caRE nO, Hp cOmputER phOnE numbER, Hp tEch hElp, Hp pc suppORt numbER, Hp laptOp custOmER suppORt, Hp dEsktOp suppORt numbER, suppORt Hp pRintER, Hp suppORt hOuRs, numbER fOR Hp suppORt, Hp suppORt custOmER sERvicE numbER, Hp cOntact phOnE numbER, custOmER sERvicE numbER fOR Hp pRintERs, Hp cOmputERs hElp, Hp tEch suppORt cOntact numbER, Hp phOnE suppORt numbER Most Urgent 1 800 784 6124 Hp printer support phone number hp printer customer care phone number HpPRinterTechSupportPhoneNumber1-800-784 6124HpPrinterSupportPhoneNumber,HpPrinterSupportNumber,HpPrintertechSupportNumber..HpPrinterssupportphonenumber”-HpPrintersphonenumber) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada Hp printer tech support phone number usa!!+++++1-800-784-6124+++Hp printer tech support phone number usa...PDF, Hp printer 1-800-784-6124 Hp printer customer service phone number,Hp printer technical support number1-800-784-6124 Hp printer customer service phone number,cannon printer helpline, Hp printer technical support phone number, Hp printer tech support number,Hp 1-800-784-6124Hp printer helpline, Hp printer technical support phone number, Hp printer tech support number 1-800-784-6124 Hp PRINTER tech support phone number USA !!Call aus 1-800-784-6124Hp Tech Support Phone Number UK-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, Hp support support, 1-800-784-6124 Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, Hp support customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, Hp support printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, Hp support phone number, Hp printer customer service, Hp printer tech support number, Hp product support 1-800-784-6124 , Hp support customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support1-800-784-6124, Hp support tech support, Hp online chat, Hp support technical support, Hp printer help line, phone number for Hp support, Hp support support phone number 1-800-784-6124, Hp printer technical support, Hp support customer service number, Hp service number, Hp support helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1-800-784-6124 number, Hp support phone, Hp support line, Hp support contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, Hp support support number, Hp support tech support number, Hp support telephone number, Hp support tech support phone number, call Hp, Hp contact support, Hp support technical support phone number, Hp support centre, Hp support customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, Hp support help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers1-800-784-6124, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact Hp support by phone, Hp printer phone support, Hp support printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, Hp support customer service telephone number, phone number for Hp support, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, Hp support customer service phone, Hp laptop tech support, Hp service phone number, Hp support printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 1-800-784-6124number, Hp support technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact Hp support, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, Hp support telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, Hp support contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, Hp support printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, Hp support help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, Hp support support center, Hp laptop customer care no, Hp printer support telephone number, Hp support services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, Hp support customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, Hp support printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for Hp support customer service, Hp support 1-800-784-6124 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 1-800-784-6124 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, Hp support computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ • EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHON
> Files
> Filter
> NameModified
> (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7130) PersistenceProperty specified in @PersistenceContext should be passed to the created EntityManager
by Scott Marlow (JIRA)
Scott Marlow created WFLY-7130:
----------------------------------
Summary: PersistenceProperty specified in @PersistenceContext should be passed to the created EntityManager
Key: WFLY-7130
URL: https://issues.jboss.org/browse/WFLY-7130
Project: WildFly
Issue Type: Bug
Affects Versions: 10.1.0.Final, JBoss AS7 7.1.1.Final
Reporter: Scott Marlow
Assignee: Jason Greene
While working on the unit test for WFLY-7075, I noticed that PersistenceContext properties are not being passed correctly to the Injected EntityManager, we should fix that.
For Example:
{quote}
@PersistenceContext(type = PersistenceContextType.TRANSACTION, unitName = "mypc", properties={@PersistenceProperty(name="wildfly.jpa.allowjoinedunsync", value="true")})
private EntityManager allowjoinedunsyncEm;
{quote}
Is passing an incorrect form of the property values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBAS-9582) Support us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/JBAS-9582?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar deleted JBAS-9582:
------------------------------
> Support us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-9582
> URL: https://issues.jboss.org/browse/JBAS-9582
> Project: Application Server 3 4 5 and 6
> Issue Type: Feature Request
> Environment: Support us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> Reporter: jira mira
>
> Support us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
> @ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 Meri Mehbooba @ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 usaHow @@cow hp printer support phone number 1 800 784 6124 hp printer support phone number usa How @@@@how 1 800 784 6124 Hp printer support phone number@@@!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA&&&!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA Testing 1 800 784 6124 Hp printer support phone number hp printer phone number status @PrinTer .1-800-784-6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa $$$$ CALL%%%%%!!!!!!!!Hp Printer tech Support Number @1-800-784-6124@ Hp Printer Tech Support Phone Number Call wireless 1-800-784-6124 1-800- 784-6124 Hp Tech Support Phone Number Canada Hp printer customer service number1-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, hewlett packard support, Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, hewlett packard customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, hewlett packard printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, hewlett packard phone number, Hp printer customer service, Hp printer tech support number, Hp product support, hewlett packard customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support, hewlett packard tech support, Hp online chat, hewlett packard technical support, Hp printer help line, phone number for Hp support, hewlett packard support phone number, Hp printer technical support, hewlett packard customer service number, Hp service number, hewlett packard helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1800 number, Hp support phone, Hp support line, hewlett packard contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, hewlett packard support number, hewlett packard tech support number, Hp support telephone number, hewlett packard tech support phone number, call Hp, Hp contact support, hewlett packard technical support phone number, Hp support centre, hewlett packard customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, hewlett packard help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact hewlett packard by phone, Hp printer phone support, hewlett packard printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, hewlett packard customer service telephone number, phone number for hewlett packard, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, hewlett packard customer service phone, Hp laptop tech support, Hp service phone number, hewlett packard printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 800 number, hewlett packard technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact hewlett packard, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, hewlett packard telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, hewlett packard contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, hewlett packard printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, hewlett packard help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, hewlett packard support center, Hp laptop customer care no, Hp printer support telephone number, Hp support 1 800 247 1987 services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, hewlett packard customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, hewlett packard printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for hewlett packard customer service, hewlett packard 800 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 800 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, hewlett packard computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, contact Hp laptop support, Hp customer service contact number, support for Hp printer, Hp printer customer care no, 1 800 247 1987 Hp computer phone number, Hp tech help, Hp pc support number, Hp laptop customer support, Hp desktop support number, support Hp printer, Hp support hours, number for Hp support, Hp support customer service number, Hp contact phone number, customer service number for Hp printers, Hp computers help, Hp tech support contact number, Hp phone support Tech vew sUpP0RT.... Hp @PrinTer .1-800-7846124- .Support Phone Number,HP printer tech support number, HP Printer Customer Care Phone Number uSa. $UPP0RT.... Hp @PrinTer .1-800-784-6124- .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa. HppRintERTEchSuppORtphOnENumbER1-800-784-6124HppRintERSuppORtphOnENumbER,HppRintERSuppORtNumbER,HppRintERtEchSuppORtNumbER..HppRintERssuppORtphOnEnumbER”-HppRintERsphOnEnumbER) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada Hp pRintER tEch suppORt phOnE numbER usa!!+++++1-800-784-6124+++Hp pRintER tEch suppORt phOnE numbER usa...pDF, Hp pRintER 1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,Hp pRintER tEchnical suppORt numbER1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,cannOn pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER,Hp 1-800-784-6124Hp pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER 1-800-784-6124 Hp pRINTER tEch suppORt phOnE numbER USA !!Call aus 1-800-784-6124Hp TEch SuppORt phOnE NumbER UK-800-784-6124 Hp suppORt numbER, Hp suppORt, Hp pRintER suppORt, Hp tEch suppORt, Hp tEchnical suppORt, Hp custOmER sERvicE numbER, Hp custOmER sERvicE, Hp tEch suppORt numbER, Hp suppORt cEntER, Hp pRintER suppORt numbER, Hp suppORt suppORt, 1-800-784-6124 Hp cOntact numbER, Hp phOnE numbER, Hp hElp and suppORt, Hp custOmER suppORt, Hp pRintER hElp, Hp tEchnical suppORt numbER, Hp suppORt phOnE numbER, Hp suppORt custOmER sERvicE, Hp pRintERs suppORt, Hp custOmER sERvicE phOnE numbER, Hp numbER, Hp custOmER caRE, Hp cOntact, Hp tEch suppORt phOnE numbER, Hp suppORt chat, Hp custOmER suppORt numbER, Hp custOmER caRE numbER, cOntact Hp suppORt, Hp hElp, Hp phOnE, Hp pRintER suppORt phOnE numbER, Hp custOmER suppORt phOnE numbER, Hp pRintER tEch suppORt, Hp phOnE suppORt, Hp tEchnical suppORt phOnE numbER, Hp laptOp suppORt numbER, Hp suppORt pRintER suppORt, Hp hElplinE, Hp tElEphOnE suppORt, Hp OnlinE suppORt, Hp suppORt cOntact, Hp chat suppORt, Hp suppORt phOnE numbER, Hp pRintER custOmER sERvicE, Hp pRintER tEch suppORt numbER, Hp pROduct suppORt 1-800-784-6124 , Hp suppORt custOmER sERvicE phOnE numbER, Hp cOmputER suppORt numbER, Hp suppORt cOntact numbER, Hp suppORt pRintER, Hp cOmputER suppORt, Hp tEch suppORt chat, Hp hElplinE numbER, Hp laptOp suppORt1-800-784-6124, Hp suppORt tEch suppORt, Hp OnlinE chat, Hp suppORt tEchnical suppORt, Hp pRintER hElp linE, phOnE numbER fOR Hp suppORt, Hp suppORt suppORt phOnE numbER 1-800-784-6124, Hp pRintER tEchnical suppORt, Hp suppORt custOmER sERvicE numbER, Hp sERvicE numbER, Hp suppORt hElplinE, Hp custOmER caRE nO, Hp pRintER custOmER sERvicE numbER, Hp hElp numbER, Hp pRintER custOmER sERvicE phOnE numbER, Hp 1-800-784-6124 numbER, Hp suppORt phOnE, Hp suppORt linE, Hp suppORt cOntact numbER, Hp pRintER tEch suppORt phOnE numbER, Hp pRintER custOmER suppORt phOnE numbER, Hp pRintERs hElp, call Hp suppORt, Hp pRintER suppORt chat, Hp suppORt suppORt numbER, Hp suppORt tEch suppORt numbER, Hp suppORt tElEphOnE numbER, Hp suppORt tEch suppORt phOnE numbER, call Hp, Hp cOntact suppORt, Hp suppORt tEchnical suppORt phOnE numbER, Hp suppORt cEntRE, Hp suppORt custOmER suppORt, Hp dEsktOp suppORt, Hp laptOp custOmER sERvicE, cOntact Hp pRintER suppORt, Hp pc suppORt, Hp laptOp custOmER caRE numbER, Hp suppORt fOR pRintERs, Hp pRintER custOmER caRE, Hp custOmER caRE phOnE numbER, Hp suppORt hElp, phOnE numbER fOR Hp, Hp OnlinE hElp, Hp laptOp custOmER caRE, Hp hElplinE phOnE numbER, Hp pRintER custOmER suppORt, Hp tEchnical suppORt chat, Hp cOmputER hElp, Hp suppORt numbERs, Hp tEchnical suppORt cOntact numbER, Hp tElEphOnE numbER, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER hElplinE, Hp suppORt pRintERs1-800-784-6124, Hp suppORt OnlinE, Hp pRintER cOntact numbER, Hp hElp phOnE numbER, Hp pRintER custOmER caRE numbER, cOntact Hp suppORt by phOnE, Hp pRintER phOnE suppORt, Hp suppORt pRintERs suppORt, Hp tEch suppORt phOnE, Hp tEchnical hElp, Hp laptOp tEch suppORt numbER, cOntact Hp by phOnE, Hp suppORt call, Hp cOmputERs suppORt, Hp suppORt custOmER sERvicE tElEphOnE numbER, phOnE numbER fOR Hp suppORt, Hp OnlinE suppORt chat, Hp laptOp custOmER sERvicE numbER, Hp OnlinE chat suppORt, Hp pRintERs custOmER sERvicE, Hp suppORt custOmER sERvicE phOnE, Hp laptOp tEch suppORt, Hp sERvicE phOnE numbER, Hp suppORt pRintER hElp, phOnE numbER fOR Hp pRintERs, Hp tROublEshOOting phOnE numbER, Hp 1-800-784-6124numbER, Hp suppORt tEchnical suppORt numbER, cOntact Hp suppORt phOnE, phOnE numbER fOR Hp pRintER suppORt, Hp custOmER suppORt chat, Hp hElp and suppORt numbER, cOntact Hp suppORt, Hp laptOp suppORt phOnE numbER, Hp pRintERs custOmER sERvicE phOnE numbER, Hp laptOp custOmER sERvicE phOnE numbER, Hp cOmputER suppORt phOnE numbER, Hp paviliOn suppORt, Hp cOmputER custOmER sERvicE, Hp custOmER sERvicEs, Hp suppORt tElEphOnE numbER, Hp hElplinE nO, Hp hElp dEsk numbER, cOntact Hp suppORt phOnE numbER, Hp suppORt cOntact, Hp phOnE numbERs, Hp pRintERs custOmER caRE numbER, Hp pRintER hElp and suppORt, cOntact Hp tEchnical suppORt, Hp cOntact numbERs, cOntact Hp suppORt chat, call Hp tEch suppORt, Hp custOmER sERvicE phOnE, Hp hElp suppORt, Hp cOmputER tEch suppORt, Hp assistancE phOnE numbER, Hp custOmER sERvicE tElEphOnE numbER, Hp suppORt pRintER suppORt phOnE numbER, Hp cOntact suppORt numbER, Hp suppORt cEntER phOnE numbER, Hp suppORt phOnE numbERs, tEch suppORt fOR Hp, Hp it suppORt, Hp laptOp hElplinE, Hp tEchnical, Hp laptOp tEchnical suppORt numbER, Hp pRintERs tEch suppORt phOnE numbER, Hp pRintERs suppORt phOnE numbER, Hp suppORt hElp dEsk phOnE numbER, Hp cOmputER tEch suppORt phOnE numbER, Hp custOmER sERvicE numbER fOR laptOp, Hp pRintER hElplinE numbER, cOntact Hp suppORt by phOnE, Hp suppORt suppORt cEntER, Hp laptOp custOmER caRE nO, Hp pRintER suppORt tElEphOnE numbER, Hp suppORt sERvicEs, Hp custOmER sERvicE numbER fOR pRintERs, Hp pROduct suppORt numbER, Hp laptOp tEch suppORt phOnE numbER, Hp pRintER hElplinE phOnE numbER, cOntact Hp custOmER suppORt, Hp suppORt custOmER suppORt phOnE numbER, Hp pRintERs tEchnical suppORt, Hp custOmER caRE cEntER, suppORt fOR Hp pRintERs, Hp pRintER suppORt cEntER, phOnE numbER fOR Hp tEch suppORt, Hp dEsktOp custOmER caRE numbER, Hp laptOps suppORt, Hp pRintER OnlinE suppORt, Hp pRintER phOnE numbER, Hp suppORt pRintERs suppORt phOnE numbER, tEchnical suppORt fOR Hp pRintERs phOnE numbER, Hp hElp cEntER phOnE numbER, cOntact Hp tEch suppORt, call Hp pRintER suppORt, Hp pRintERs custOmER suppORt, Hp cOmputER custOmER sERvicE numbER, Hp pRintERs hElplinE, Hp custOmER caRE cOntact numbER, Hp laptOp hElp, Hp cOmputER custOmER sERvicE phOnE numbER, phOnE numbER fOR Hp suppORt custOmER sERvicE, Hp suppORt 1-800-784-6124 numbER, Hp pRintER hElp phOnE numbER, Hp pRintERs hElp phOnE numbER, Hp pRintER phOnE numbER fOR custOmER sERvicE, Hp cOmputER tEchnical suppORt phOnE numbER, custOmER sERvicE Hp, Hp suppORt tEchnical suppORt numbER, cOntact numbER fOR Hp, Hp cOmputERs suppORt phOnE numbER, Hp pRintERs suppORt numbER, Hp pRintER tEchnical suppORt numbER, cOntact Hp tEch suppORt by phOnE, Hp cOmputER custOmER caRE numbER, Hp pRintER 1-800-784-6124 numbER, call Hp custOmER sERvicE, Hp pRintER hElp cEntER, Hp cOmputERs custOmER sERvicE, Hp pRintER hElp dEsk, Hp suppORt cOmputER suppORt, Hp pRintERs tEchnical suppORt numbER, Hp hElp dEsk phOnE numbER, Hp pRintER suppORt phOnE, Hp cOntact hElp, cOntact Hp laptOp suppORt, Hp custOmER sERvicE cOntact numbER, suppORt fOR Hp pRintER, Hp pRintER custOmER caRE nO, Hp cOmputER phOnE numbER, Hp tEch hElp, Hp pc suppORt numbER, Hp laptOp custOmER suppORt, Hp dEsktOp suppORt numbER, suppORt Hp pRintER, Hp suppORt hOuRs, numbER fOR Hp suppORt, Hp suppORt custOmER sERvicE numbER, Hp cOntact phOnE numbER, custOmER sERvicE numbER fOR Hp pRintERs, Hp cOmputERs hElp, Hp tEch suppORt cOntact numbER, Hp phOnE suppORt numbER Most Urgent 1 800 784 6124 Hp printer support phone number hp printer customer care phone number HpPRinterTechSupportPhoneNumber1-800-784 6124HpPrinterSupportPhoneNumber,HpPrinterSupportNumber,HpPrintertechSupportNumber..HpPrinterssupportphonenumber”-HpPrintersphonenumber) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada Hp printer tech support phone number usa!!+++++1-800-784-6124+++Hp printer tech support phone number usa...PDF, Hp printer 1-800-784-6124 Hp printer customer service phone number,Hp printer technical support number1-800-784-6124 Hp printer customer service phone number,cannon printer helpline, Hp printer technical support phone number, Hp printer tech support number,Hp 1-800-784-6124Hp printer helpline, Hp printer technical support phone number, Hp printer tech support number 1-800-784-6124 Hp PRINTER tech support phone number USA !!Call aus 1-800-784-6124Hp Tech Support Phone Number UK-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, Hp support support, 1-800-784-6124 Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, Hp support customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, Hp support printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, Hp support phone number, Hp printer customer service, Hp printer tech support number, Hp product support 1-800-784-6124 , Hp support customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support1-800-784-6124, Hp support tech support, Hp online chat, Hp support technical support, Hp printer help line, phone number for Hp support, Hp support support phone number 1-800-784-6124, Hp printer technical support, Hp support customer service number, Hp service number, Hp support helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1-800-784-6124 number, Hp support phone, Hp support line, Hp support contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, Hp support support number, Hp support tech support number, Hp support telephone number, Hp support tech support phone number, call Hp, Hp contact support, Hp support technical support phone number, Hp support centre, Hp support customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, Hp support help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers1-800-784-6124, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact Hp support by phone, Hp printer phone support, Hp support printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, Hp support customer service telephone number, phone number for Hp support, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, Hp support customer service phone, Hp laptop tech support, Hp service phone number, Hp support printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 1-800-784-6124number, Hp support technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact Hp support, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, Hp support telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, Hp support contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, Hp support printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, Hp support help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, Hp support support center, Hp laptop customer care no, Hp printer support telephone number, Hp support services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, Hp support customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, Hp support printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for Hp support customer service, Hp support 1-800-784-6124 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 1-800-784-6124 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, Hp support computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ • EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHON
> Files
> Filter
> NameModified
> (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7129) Removing XA Datasources via CLI OR DMR does not de-register it from the context without reload.
by shailendra singh (JIRA)
shailendra singh created WFLY-7129:
--------------------------------------
Summary: Removing XA Datasources via CLI OR DMR does not de-register it from the context without reload.
Key: WFLY-7129
URL: https://issues.jboss.org/browse/WFLY-7129
Project: WildFly
Issue Type: Bug
Components: Domain Management, JCA
Affects Versions: 10.1.0.Final
Reporter: shailendra singh
Assignee: Brian Stansberry
Priority: Minor
Below is the result of add .. remove ..add operation of XADatasource .
1. Add - OK
{code:java}
[domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:add(jndi-name=java\:jboss\/datasources\/oracleXaDatasource,driver-name=oracle-driver.jar)
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
{code}
2. Remove - OK
{code:java}
[domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:remove()
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
{code}
3. Add - Error is thrown
{code:java}
[domain@localhost:9990 /] ./profile=default/subsystem=datasources/xa-data-source=TestXADataSource:add(jndi-name=java\:jboss\/datasources\/oracleXaDatasource,driver-name=oracle-driver.jar)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.data-source.TestXADataSource' is already registered in context 'profile=default'."},
"rolled-back" => true
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBAS-9584) (1.8.0.0(.7.8.4 6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
by jira mira (JIRA)
jira mira created JBAS-9584:
-------------------------------
Summary: (1.8.0.0(.7.8.4 6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
Key: JBAS-9584
URL: https://issues.jboss.org/browse/JBAS-9584
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Environment: (1.8.0.0(.7.8.4 6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
Reporter: jira mira
(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
@ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 Meri Mehbooba @ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 usaHow @@cow hp printer support phone number 1 800 784 6124 hp printer support phone number usa How @@@@how 1 800 784 6124 Hp printer support phone number@@@!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA&&&!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA Testing 1 800 784 6124 Hp printer support phone number hp printer phone number status @PrinTer .1-800-784-6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa $$$$ CALL%%%%%!!!!!!!!Hp Printer tech Support Number @1-800-784-6124@ Hp Printer Tech Support Phone Number Call wireless 1-800-784-6124 1-800- 784-6124 Hp Tech Support Phone Number Canada Hp printer customer service number1-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, hewlett packard support, Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, hewlett packard customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, hewlett packard printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, hewlett packard phone number, Hp printer customer service, Hp printer tech support number, Hp product support, hewlett packard customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support, hewlett packard tech support, Hp online chat, hewlett packard technical support, Hp printer help line, phone number for Hp support, hewlett packard support phone number, Hp printer technical support, hewlett packard customer service number, Hp service number, hewlett packard helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1800 number, Hp support phone, Hp support line, hewlett packard contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, hewlett packard support number, hewlett packard tech support number, Hp support telephone number, hewlett packard tech support phone number, call Hp, Hp contact support, hewlett packard technical support phone number, Hp support centre, hewlett packard customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, hewlett packard help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact hewlett packard by phone, Hp printer phone support, hewlett packard printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, hewlett packard customer service telephone number, phone number for hewlett packard, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, hewlett packard customer service phone, Hp laptop tech support, Hp service phone number, hewlett packard printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 800 number, hewlett packard technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact hewlett packard, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, hewlett packard telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, hewlett packard contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, hewlett packard printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, hewlett packard help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, hewlett packard support center, Hp laptop customer care no, Hp printer support telephone number, Hp support 1 800 247 1987 services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, hewlett packard customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, hewlett packard printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for hewlett packard customer service, hewlett packard 800 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 800 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, hewlett packard computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, contact Hp laptop support, Hp customer service contact number, support for Hp printer, Hp printer customer care no, 1 800 247 1987 Hp computer phone number, Hp tech help, Hp pc support number, Hp laptop customer support, Hp desktop support number, support Hp printer, Hp support hours, number for Hp support, Hp support customer service number, Hp contact phone number, customer service number for Hp printers, Hp computers help, Hp tech support contact number, Hp phone support Tech vew sUpP0RT.... Hp @PrinTer .1-800-7846124- .Support Phone Number,HP printer tech support number, HP Printer Customer Care Phone Number uSa. $UPP0RT.... Hp @PrinTer .1-800-784-6124- .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa. HppRintERTEchSuppORtphOnENumbER1-800-784-6124HppRintERSuppORtphOnENumbER,HppRintERSuppORtNumbER,HppRintERtEchSuppORtNumbER..HppRintERssuppORtphOnEnumbER”-HppRintERsphOnEnumbER) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada Hp pRintER tEch suppORt phOnE numbER usa!!+++++1-800-784-6124+++Hp pRintER tEch suppORt phOnE numbER usa...pDF, Hp pRintER 1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,Hp pRintER tEchnical suppORt numbER1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,cannOn pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER,Hp 1-800-784-6124Hp pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER 1-800-784-6124 Hp pRINTER tEch suppORt phOnE numbER USA !!Call aus 1-800-784-6124Hp TEch SuppORt phOnE NumbER UK-800-784-6124 Hp suppORt numbER, Hp suppORt, Hp pRintER suppORt, Hp tEch suppORt, Hp tEchnical suppORt, Hp custOmER sERvicE numbER, Hp custOmER sERvicE, Hp tEch suppORt numbER, Hp suppORt cEntER, Hp pRintER suppORt numbER, Hp suppORt suppORt, 1-800-784-6124 Hp cOntact numbER, Hp phOnE numbER, Hp hElp and suppORt, Hp custOmER suppORt, Hp pRintER hElp, Hp tEchnical suppORt numbER, Hp suppORt phOnE numbER, Hp suppORt custOmER sERvicE, Hp pRintERs suppORt, Hp custOmER sERvicE phOnE numbER, Hp numbER, Hp custOmER caRE, Hp cOntact, Hp tEch suppORt phOnE numbER, Hp suppORt chat, Hp custOmER suppORt numbER, Hp custOmER caRE numbER, cOntact Hp suppORt, Hp hElp, Hp phOnE, Hp pRintER suppORt phOnE numbER, Hp custOmER suppORt phOnE numbER, Hp pRintER tEch suppORt, Hp phOnE suppORt, Hp tEchnical suppORt phOnE numbER, Hp laptOp suppORt numbER, Hp suppORt pRintER suppORt, Hp hElplinE, Hp tElEphOnE suppORt, Hp OnlinE suppORt, Hp suppORt cOntact, Hp chat suppORt, Hp suppORt phOnE numbER, Hp pRintER custOmER sERvicE, Hp pRintER tEch suppORt numbER, Hp pROduct suppORt 1-800-784-6124 , Hp suppORt custOmER sERvicE phOnE numbER, Hp cOmputER suppORt numbER, Hp suppORt cOntact numbER, Hp suppORt pRintER, Hp cOmputER suppORt, Hp tEch suppORt chat, Hp hElplinE numbER, Hp laptOp suppORt1-800-784-6124, Hp suppORt tEch suppORt, Hp OnlinE chat, Hp suppORt tEchnical suppORt, Hp pRintER hElp linE, phOnE numbER fOR Hp suppORt, Hp suppORt suppORt phOnE numbER 1-800-784-6124, Hp pRintER tEchnical suppORt, Hp suppORt custOmER sERvicE numbER, Hp sERvicE numbER, Hp suppORt hElplinE, Hp custOmER caRE nO, Hp pRintER custOmER sERvicE numbER, Hp hElp numbER, Hp pRintER custOmER sERvicE phOnE numbER, Hp 1-800-784-6124 numbER, Hp suppORt phOnE, Hp suppORt linE, Hp suppORt cOntact numbER, Hp pRintER tEch suppORt phOnE numbER, Hp pRintER custOmER suppORt phOnE numbER, Hp pRintERs hElp, call Hp suppORt, Hp pRintER suppORt chat, Hp suppORt suppORt numbER, Hp suppORt tEch suppORt numbER, Hp suppORt tElEphOnE numbER, Hp suppORt tEch suppORt phOnE numbER, call Hp, Hp cOntact suppORt, Hp suppORt tEchnical suppORt phOnE numbER, Hp suppORt cEntRE, Hp suppORt custOmER suppORt, Hp dEsktOp suppORt, Hp laptOp custOmER sERvicE, cOntact Hp pRintER suppORt, Hp pc suppORt, Hp laptOp custOmER caRE numbER, Hp suppORt fOR pRintERs, Hp pRintER custOmER caRE, Hp custOmER caRE phOnE numbER, Hp suppORt hElp, phOnE numbER fOR Hp, Hp OnlinE hElp, Hp laptOp custOmER caRE, Hp hElplinE phOnE numbER, Hp pRintER custOmER suppORt, Hp tEchnical suppORt chat, Hp cOmputER hElp, Hp suppORt numbERs, Hp tEchnical suppORt cOntact numbER, Hp tElEphOnE numbER, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER hElplinE, Hp suppORt pRintERs1-800-784-6124, Hp suppORt OnlinE, Hp pRintER cOntact numbER, Hp hElp phOnE numbER, Hp pRintER custOmER caRE numbER, cOntact Hp suppORt by phOnE, Hp pRintER phOnE suppORt, Hp suppORt pRintERs suppORt, Hp tEch suppORt phOnE, Hp tEchnical hElp, Hp laptOp tEch suppORt numbER, cOntact Hp by phOnE, Hp suppORt call, Hp cOmputERs suppORt, Hp suppORt custOmER sERvicE tElEphOnE numbER, phOnE numbER fOR Hp suppORt, Hp OnlinE suppORt chat, Hp laptOp custOmER sERvicE numbER, Hp OnlinE chat suppORt, Hp pRintERs custOmER sERvicE, Hp suppORt custOmER sERvicE phOnE, Hp laptOp tEch suppORt, Hp sERvicE phOnE numbER, Hp suppORt pRintER hElp, phOnE numbER fOR Hp pRintERs, Hp tROublEshOOting phOnE numbER, Hp 1-800-784-6124numbER, Hp suppORt tEchnical suppORt numbER, cOntact Hp suppORt phOnE, phOnE numbER fOR Hp pRintER suppORt, Hp custOmER suppORt chat, Hp hElp and suppORt numbER, cOntact Hp suppORt, Hp laptOp suppORt phOnE numbER, Hp pRintERs custOmER sERvicE phOnE numbER, Hp laptOp custOmER sERvicE phOnE numbER, Hp cOmputER suppORt phOnE numbER, Hp paviliOn suppORt, Hp cOmputER custOmER sERvicE, Hp custOmER sERvicEs, Hp suppORt tElEphOnE numbER, Hp hElplinE nO, Hp hElp dEsk numbER, cOntact Hp suppORt phOnE numbER, Hp suppORt cOntact, Hp phOnE numbERs, Hp pRintERs custOmER caRE numbER, Hp pRintER hElp and suppORt, cOntact Hp tEchnical suppORt, Hp cOntact numbERs, cOntact Hp suppORt chat, call Hp tEch suppORt, Hp custOmER sERvicE phOnE, Hp hElp suppORt, Hp cOmputER tEch suppORt, Hp assistancE phOnE numbER, Hp custOmER sERvicE tElEphOnE numbER, Hp suppORt pRintER suppORt phOnE numbER, Hp cOntact suppORt numbER, Hp suppORt cEntER phOnE numbER, Hp suppORt phOnE numbERs, tEch suppORt fOR Hp, Hp it suppORt, Hp laptOp hElplinE, Hp tEchnical, Hp laptOp tEchnical suppORt numbER, Hp pRintERs tEch suppORt phOnE numbER, Hp pRintERs suppORt phOnE numbER, Hp suppORt hElp dEsk phOnE numbER, Hp cOmputER tEch suppORt phOnE numbER, Hp custOmER sERvicE numbER fOR laptOp, Hp pRintER hElplinE numbER, cOntact Hp suppORt by phOnE, Hp suppORt suppORt cEntER, Hp laptOp custOmER caRE nO, Hp pRintER suppORt tElEphOnE numbER, Hp suppORt sERvicEs, Hp custOmER sERvicE numbER fOR pRintERs, Hp pROduct suppORt numbER, Hp laptOp tEch suppORt phOnE numbER, Hp pRintER hElplinE phOnE numbER, cOntact Hp custOmER suppORt, Hp suppORt custOmER suppORt phOnE numbER, Hp pRintERs tEchnical suppORt, Hp custOmER caRE cEntER, suppORt fOR Hp pRintERs, Hp pRintER suppORt cEntER, phOnE numbER fOR Hp tEch suppORt, Hp dEsktOp custOmER caRE numbER, Hp laptOps suppORt, Hp pRintER OnlinE suppORt, Hp pRintER phOnE numbER, Hp suppORt pRintERs suppORt phOnE numbER, tEchnical suppORt fOR Hp pRintERs phOnE numbER, Hp hElp cEntER phOnE numbER, cOntact Hp tEch suppORt, call Hp pRintER suppORt, Hp pRintERs custOmER suppORt, Hp cOmputER custOmER sERvicE numbER, Hp pRintERs hElplinE, Hp custOmER caRE cOntact numbER, Hp laptOp hElp, Hp cOmputER custOmER sERvicE phOnE numbER, phOnE numbER fOR Hp suppORt custOmER sERvicE, Hp suppORt 1-800-784-6124 numbER, Hp pRintER hElp phOnE numbER, Hp pRintERs hElp phOnE numbER, Hp pRintER phOnE numbER fOR custOmER sERvicE, Hp cOmputER tEchnical suppORt phOnE numbER, custOmER sERvicE Hp, Hp suppORt tEchnical suppORt numbER, cOntact numbER fOR Hp, Hp cOmputERs suppORt phOnE numbER, Hp pRintERs suppORt numbER, Hp pRintER tEchnical suppORt numbER, cOntact Hp tEch suppORt by phOnE, Hp cOmputER custOmER caRE numbER, Hp pRintER 1-800-784-6124 numbER, call Hp custOmER sERvicE, Hp pRintER hElp cEntER, Hp cOmputERs custOmER sERvicE, Hp pRintER hElp dEsk, Hp suppORt cOmputER suppORt, Hp pRintERs tEchnical suppORt numbER, Hp hElp dEsk phOnE numbER, Hp pRintER suppORt phOnE, Hp cOntact hElp, cOntact Hp laptOp suppORt, Hp custOmER sERvicE cOntact numbER, suppORt fOR Hp pRintER, Hp pRintER custOmER caRE nO, Hp cOmputER phOnE numbER, Hp tEch hElp, Hp pc suppORt numbER, Hp laptOp custOmER suppORt, Hp dEsktOp suppORt numbER, suppORt Hp pRintER, Hp suppORt hOuRs, numbER fOR Hp suppORt, Hp suppORt custOmER sERvicE numbER, Hp cOntact phOnE numbER, custOmER sERvicE numbER fOR Hp pRintERs, Hp cOmputERs hElp, Hp tEch suppORt cOntact numbER, Hp phOnE suppORt numbER Most Urgent 1 800 784 6124 Hp printer support phone number hp printer customer care phone number HpPRinterTechSupportPhoneNumber1-800-784 6124HpPrinterSupportPhoneNumber,HpPrinterSupportNumber,HpPrintertechSupportNumber..HpPrinterssupportphonenumber”-HpPrintersphonenumber) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada Hp printer tech support phone number usa!!+++++1-800-784-6124+++Hp printer tech support phone number usa...PDF, Hp printer 1-800-784-6124 Hp printer customer service phone number,Hp printer technical support number1-800-784-6124 Hp printer customer service phone number,cannon printer helpline, Hp printer technical support phone number, Hp printer tech support number,Hp 1-800-784-6124Hp printer helpline, Hp printer technical support phone number, Hp printer tech support number 1-800-784-6124 Hp PRINTER tech support phone number USA !!Call aus 1-800-784-6124Hp Tech Support Phone Number UK-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, Hp support support, 1-800-784-6124 Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, Hp support customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, Hp support printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, Hp support phone number, Hp printer customer service, Hp printer tech support number, Hp product support 1-800-784-6124 , Hp support customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support1-800-784-6124, Hp support tech support, Hp online chat, Hp support technical support, Hp printer help line, phone number for Hp support, Hp support support phone number 1-800-784-6124, Hp printer technical support, Hp support customer service number, Hp service number, Hp support helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1-800-784-6124 number, Hp support phone, Hp support line, Hp support contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, Hp support support number, Hp support tech support number, Hp support telephone number, Hp support tech support phone number, call Hp, Hp contact support, Hp support technical support phone number, Hp support centre, Hp support customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, Hp support help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers1-800-784-6124, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact Hp support by phone, Hp printer phone support, Hp support printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, Hp support customer service telephone number, phone number for Hp support, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, Hp support customer service phone, Hp laptop tech support, Hp service phone number, Hp support printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 1-800-784-6124number, Hp support technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact Hp support, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, Hp support telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, Hp support contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, Hp support printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, Hp support help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, Hp support support center, Hp laptop customer care no, Hp printer support telephone number, Hp support services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, Hp support customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, Hp support printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for Hp support customer service, Hp support 1-800-784-6124 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 1-800-784-6124 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, Hp support computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ • EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHON
Files
Filter
NameModified
(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBAS-9583) (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
by jira mira (JIRA)
jira mira created JBAS-9583:
-------------------------------
Summary: (1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
Key: JBAS-9583
URL: https://issues.jboss.org/browse/JBAS-9583
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Environment:
(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
Reporter: jira mira
(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT
@ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 Meri Mehbooba @ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 usaHow @@cow hp printer support phone number 1 800 784 6124 hp printer support phone number usa How @@@@how 1 800 784 6124 Hp printer support phone number@@@!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA&&&!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA Testing 1 800 784 6124 Hp printer support phone number hp printer phone number status @PrinTer .1-800-784-6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa $$$$ CALL%%%%%!!!!!!!!Hp Printer tech Support Number @1-800-784-6124@ Hp Printer Tech Support Phone Number Call wireless 1-800-784-6124 1-800- 784-6124 Hp Tech Support Phone Number Canada Hp printer customer service number1-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, hewlett packard support, Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, hewlett packard customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, hewlett packard printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, hewlett packard phone number, Hp printer customer service, Hp printer tech support number, Hp product support, hewlett packard customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support, hewlett packard tech support, Hp online chat, hewlett packard technical support, Hp printer help line, phone number for Hp support, hewlett packard support phone number, Hp printer technical support, hewlett packard customer service number, Hp service number, hewlett packard helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1800 number, Hp support phone, Hp support line, hewlett packard contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, hewlett packard support number, hewlett packard tech support number, Hp support telephone number, hewlett packard tech support phone number, call Hp, Hp contact support, hewlett packard technical support phone number, Hp support centre, hewlett packard customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, hewlett packard help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact hewlett packard by phone, Hp printer phone support, hewlett packard printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, hewlett packard customer service telephone number, phone number for hewlett packard, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, hewlett packard customer service phone, Hp laptop tech support, Hp service phone number, hewlett packard printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 800 number, hewlett packard technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact hewlett packard, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, hewlett packard telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, hewlett packard contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, hewlett packard printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, hewlett packard help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, hewlett packard support center, Hp laptop customer care no, Hp printer support telephone number, Hp support 1 800 247 1987 services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, hewlett packard customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, hewlett packard printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for hewlett packard customer service, hewlett packard 800 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 800 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, hewlett packard computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, contact Hp laptop support, Hp customer service contact number, support for Hp printer, Hp printer customer care no, 1 800 247 1987 Hp computer phone number, Hp tech help, Hp pc support number, Hp laptop customer support, Hp desktop support number, support Hp printer, Hp support hours, number for Hp support, Hp support customer service number, Hp contact phone number, customer service number for Hp printers, Hp computers help, Hp tech support contact number, Hp phone support Tech vew sUpP0RT.... Hp @PrinTer .1-800-7846124- .Support Phone Number,HP printer tech support number, HP Printer Customer Care Phone Number uSa. $UPP0RT.... Hp @PrinTer .1-800-784-6124- .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa. HppRintERTEchSuppORtphOnENumbER1-800-784-6124HppRintERSuppORtphOnENumbER,HppRintERSuppORtNumbER,HppRintERtEchSuppORtNumbER..HppRintERssuppORtphOnEnumbER”-HppRintERsphOnEnumbER) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada Hp pRintER tEch suppORt phOnE numbER usa!!+++++1-800-784-6124+++Hp pRintER tEch suppORt phOnE numbER usa...pDF, Hp pRintER 1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,Hp pRintER tEchnical suppORt numbER1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,cannOn pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER,Hp 1-800-784-6124Hp pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER 1-800-784-6124 Hp pRINTER tEch suppORt phOnE numbER USA !!Call aus 1-800-784-6124Hp TEch SuppORt phOnE NumbER UK-800-784-6124 Hp suppORt numbER, Hp suppORt, Hp pRintER suppORt, Hp tEch suppORt, Hp tEchnical suppORt, Hp custOmER sERvicE numbER, Hp custOmER sERvicE, Hp tEch suppORt numbER, Hp suppORt cEntER, Hp pRintER suppORt numbER, Hp suppORt suppORt, 1-800-784-6124 Hp cOntact numbER, Hp phOnE numbER, Hp hElp and suppORt, Hp custOmER suppORt, Hp pRintER hElp, Hp tEchnical suppORt numbER, Hp suppORt phOnE numbER, Hp suppORt custOmER sERvicE, Hp pRintERs suppORt, Hp custOmER sERvicE phOnE numbER, Hp numbER, Hp custOmER caRE, Hp cOntact, Hp tEch suppORt phOnE numbER, Hp suppORt chat, Hp custOmER suppORt numbER, Hp custOmER caRE numbER, cOntact Hp suppORt, Hp hElp, Hp phOnE, Hp pRintER suppORt phOnE numbER, Hp custOmER suppORt phOnE numbER, Hp pRintER tEch suppORt, Hp phOnE suppORt, Hp tEchnical suppORt phOnE numbER, Hp laptOp suppORt numbER, Hp suppORt pRintER suppORt, Hp hElplinE, Hp tElEphOnE suppORt, Hp OnlinE suppORt, Hp suppORt cOntact, Hp chat suppORt, Hp suppORt phOnE numbER, Hp pRintER custOmER sERvicE, Hp pRintER tEch suppORt numbER, Hp pROduct suppORt 1-800-784-6124 , Hp suppORt custOmER sERvicE phOnE numbER, Hp cOmputER suppORt numbER, Hp suppORt cOntact numbER, Hp suppORt pRintER, Hp cOmputER suppORt, Hp tEch suppORt chat, Hp hElplinE numbER, Hp laptOp suppORt1-800-784-6124, Hp suppORt tEch suppORt, Hp OnlinE chat, Hp suppORt tEchnical suppORt, Hp pRintER hElp linE, phOnE numbER fOR Hp suppORt, Hp suppORt suppORt phOnE numbER 1-800-784-6124, Hp pRintER tEchnical suppORt, Hp suppORt custOmER sERvicE numbER, Hp sERvicE numbER, Hp suppORt hElplinE, Hp custOmER caRE nO, Hp pRintER custOmER sERvicE numbER, Hp hElp numbER, Hp pRintER custOmER sERvicE phOnE numbER, Hp 1-800-784-6124 numbER, Hp suppORt phOnE, Hp suppORt linE, Hp suppORt cOntact numbER, Hp pRintER tEch suppORt phOnE numbER, Hp pRintER custOmER suppORt phOnE numbER, Hp pRintERs hElp, call Hp suppORt, Hp pRintER suppORt chat, Hp suppORt suppORt numbER, Hp suppORt tEch suppORt numbER, Hp suppORt tElEphOnE numbER, Hp suppORt tEch suppORt phOnE numbER, call Hp, Hp cOntact suppORt, Hp suppORt tEchnical suppORt phOnE numbER, Hp suppORt cEntRE, Hp suppORt custOmER suppORt, Hp dEsktOp suppORt, Hp laptOp custOmER sERvicE, cOntact Hp pRintER suppORt, Hp pc suppORt, Hp laptOp custOmER caRE numbER, Hp suppORt fOR pRintERs, Hp pRintER custOmER caRE, Hp custOmER caRE phOnE numbER, Hp suppORt hElp, phOnE numbER fOR Hp, Hp OnlinE hElp, Hp laptOp custOmER caRE, Hp hElplinE phOnE numbER, Hp pRintER custOmER suppORt, Hp tEchnical suppORt chat, Hp cOmputER hElp, Hp suppORt numbERs, Hp tEchnical suppORt cOntact numbER, Hp tElEphOnE numbER, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER hElplinE, Hp suppORt pRintERs1-800-784-6124, Hp suppORt OnlinE, Hp pRintER cOntact numbER, Hp hElp phOnE numbER, Hp pRintER custOmER caRE numbER, cOntact Hp suppORt by phOnE, Hp pRintER phOnE suppORt, Hp suppORt pRintERs suppORt, Hp tEch suppORt phOnE, Hp tEchnical hElp, Hp laptOp tEch suppORt numbER, cOntact Hp by phOnE, Hp suppORt call, Hp cOmputERs suppORt, Hp suppORt custOmER sERvicE tElEphOnE numbER, phOnE numbER fOR Hp suppORt, Hp OnlinE suppORt chat, Hp laptOp custOmER sERvicE numbER, Hp OnlinE chat suppORt, Hp pRintERs custOmER sERvicE, Hp suppORt custOmER sERvicE phOnE, Hp laptOp tEch suppORt, Hp sERvicE phOnE numbER, Hp suppORt pRintER hElp, phOnE numbER fOR Hp pRintERs, Hp tROublEshOOting phOnE numbER, Hp 1-800-784-6124numbER, Hp suppORt tEchnical suppORt numbER, cOntact Hp suppORt phOnE, phOnE numbER fOR Hp pRintER suppORt, Hp custOmER suppORt chat, Hp hElp and suppORt numbER, cOntact Hp suppORt, Hp laptOp suppORt phOnE numbER, Hp pRintERs custOmER sERvicE phOnE numbER, Hp laptOp custOmER sERvicE phOnE numbER, Hp cOmputER suppORt phOnE numbER, Hp paviliOn suppORt, Hp cOmputER custOmER sERvicE, Hp custOmER sERvicEs, Hp suppORt tElEphOnE numbER, Hp hElplinE nO, Hp hElp dEsk numbER, cOntact Hp suppORt phOnE numbER, Hp suppORt cOntact, Hp phOnE numbERs, Hp pRintERs custOmER caRE numbER, Hp pRintER hElp and suppORt, cOntact Hp tEchnical suppORt, Hp cOntact numbERs, cOntact Hp suppORt chat, call Hp tEch suppORt, Hp custOmER sERvicE phOnE, Hp hElp suppORt, Hp cOmputER tEch suppORt, Hp assistancE phOnE numbER, Hp custOmER sERvicE tElEphOnE numbER, Hp suppORt pRintER suppORt phOnE numbER, Hp cOntact suppORt numbER, Hp suppORt cEntER phOnE numbER, Hp suppORt phOnE numbERs, tEch suppORt fOR Hp, Hp it suppORt, Hp laptOp hElplinE, Hp tEchnical, Hp laptOp tEchnical suppORt numbER, Hp pRintERs tEch suppORt phOnE numbER, Hp pRintERs suppORt phOnE numbER, Hp suppORt hElp dEsk phOnE numbER, Hp cOmputER tEch suppORt phOnE numbER, Hp custOmER sERvicE numbER fOR laptOp, Hp pRintER hElplinE numbER, cOntact Hp suppORt by phOnE, Hp suppORt suppORt cEntER, Hp laptOp custOmER caRE nO, Hp pRintER suppORt tElEphOnE numbER, Hp suppORt sERvicEs, Hp custOmER sERvicE numbER fOR pRintERs, Hp pROduct suppORt numbER, Hp laptOp tEch suppORt phOnE numbER, Hp pRintER hElplinE phOnE numbER, cOntact Hp custOmER suppORt, Hp suppORt custOmER suppORt phOnE numbER, Hp pRintERs tEchnical suppORt, Hp custOmER caRE cEntER, suppORt fOR Hp pRintERs, Hp pRintER suppORt cEntER, phOnE numbER fOR Hp tEch suppORt, Hp dEsktOp custOmER caRE numbER, Hp laptOps suppORt, Hp pRintER OnlinE suppORt, Hp pRintER phOnE numbER, Hp suppORt pRintERs suppORt phOnE numbER, tEchnical suppORt fOR Hp pRintERs phOnE numbER, Hp hElp cEntER phOnE numbER, cOntact Hp tEch suppORt, call Hp pRintER suppORt, Hp pRintERs custOmER suppORt, Hp cOmputER custOmER sERvicE numbER, Hp pRintERs hElplinE, Hp custOmER caRE cOntact numbER, Hp laptOp hElp, Hp cOmputER custOmER sERvicE phOnE numbER, phOnE numbER fOR Hp suppORt custOmER sERvicE, Hp suppORt 1-800-784-6124 numbER, Hp pRintER hElp phOnE numbER, Hp pRintERs hElp phOnE numbER, Hp pRintER phOnE numbER fOR custOmER sERvicE, Hp cOmputER tEchnical suppORt phOnE numbER, custOmER sERvicE Hp, Hp suppORt tEchnical suppORt numbER, cOntact numbER fOR Hp, Hp cOmputERs suppORt phOnE numbER, Hp pRintERs suppORt numbER, Hp pRintER tEchnical suppORt numbER, cOntact Hp tEch suppORt by phOnE, Hp cOmputER custOmER caRE numbER, Hp pRintER 1-800-784-6124 numbER, call Hp custOmER sERvicE, Hp pRintER hElp cEntER, Hp cOmputERs custOmER sERvicE, Hp pRintER hElp dEsk, Hp suppORt cOmputER suppORt, Hp pRintERs tEchnical suppORt numbER, Hp hElp dEsk phOnE numbER, Hp pRintER suppORt phOnE, Hp cOntact hElp, cOntact Hp laptOp suppORt, Hp custOmER sERvicE cOntact numbER, suppORt fOR Hp pRintER, Hp pRintER custOmER caRE nO, Hp cOmputER phOnE numbER, Hp tEch hElp, Hp pc suppORt numbER, Hp laptOp custOmER suppORt, Hp dEsktOp suppORt numbER, suppORt Hp pRintER, Hp suppORt hOuRs, numbER fOR Hp suppORt, Hp suppORt custOmER sERvicE numbER, Hp cOntact phOnE numbER, custOmER sERvicE numbER fOR Hp pRintERs, Hp cOmputERs hElp, Hp tEch suppORt cOntact numbER, Hp phOnE suppORt numbER Most Urgent 1 800 784 6124 Hp printer support phone number hp printer customer care phone number HpPRinterTechSupportPhoneNumber1-800-784 6124HpPrinterSupportPhoneNumber,HpPrinterSupportNumber,HpPrintertechSupportNumber..HpPrinterssupportphonenumber”-HpPrintersphonenumber) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada Hp printer tech support phone number usa!!+++++1-800-784-6124+++Hp printer tech support phone number usa...PDF, Hp printer 1-800-784-6124 Hp printer customer service phone number,Hp printer technical support number1-800-784-6124 Hp printer customer service phone number,cannon printer helpline, Hp printer technical support phone number, Hp printer tech support number,Hp 1-800-784-6124Hp printer helpline, Hp printer technical support phone number, Hp printer tech support number 1-800-784-6124 Hp PRINTER tech support phone number USA !!Call aus 1-800-784-6124Hp Tech Support Phone Number UK-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, Hp support support, 1-800-784-6124 Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, Hp support customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, Hp support printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, Hp support phone number, Hp printer customer service, Hp printer tech support number, Hp product support 1-800-784-6124 , Hp support customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support1-800-784-6124, Hp support tech support, Hp online chat, Hp support technical support, Hp printer help line, phone number for Hp support, Hp support support phone number 1-800-784-6124, Hp printer technical support, Hp support customer service number, Hp service number, Hp support helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1-800-784-6124 number, Hp support phone, Hp support line, Hp support contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, Hp support support number, Hp support tech support number, Hp support telephone number, Hp support tech support phone number, call Hp, Hp contact support, Hp support technical support phone number, Hp support centre, Hp support customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, Hp support help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers1-800-784-6124, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact Hp support by phone, Hp printer phone support, Hp support printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, Hp support customer service telephone number, phone number for Hp support, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, Hp support customer service phone, Hp laptop tech support, Hp service phone number, Hp support printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 1-800-784-6124number, Hp support technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact Hp support, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, Hp support telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, Hp support contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, Hp support printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, Hp support help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, Hp support support center, Hp laptop customer care no, Hp printer support telephone number, Hp support services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, Hp support customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, Hp support printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for Hp support customer service, Hp support 1-800-784-6124 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 1-800-784-6124 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, Hp support computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ • EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHON
Files
Filter
NameModified
(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBAS-9582) Support us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
by jira mira (JIRA)
jira mira created JBAS-9582:
-------------------------------
Summary: Support us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
Key: JBAS-9582
URL: https://issues.jboss.org/browse/JBAS-9582
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Environment: Support us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
Reporter: jira mira
Support us-24*7-1.8.0.0.7.8.4.6.1.2.4 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER%%CUSOMER &&SERVICE
@ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 Meri Mehbooba @ 1800.784 6124 HP printer tech support phone number ,HP technical support 1800.784 6124 usaHow @@cow hp printer support phone number 1 800 784 6124 hp printer support phone number usa How @@@@how 1 800 784 6124 Hp printer support phone number@@@!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA&&&!!!! hp printer PrinTer call @@@@@ .1-800 784 6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number USA Testing 1 800 784 6124 Hp printer support phone number hp printer phone number status @PrinTer .1-800-784-6124 .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa $$$$ CALL%%%%%!!!!!!!!Hp Printer tech Support Number @1-800-784-6124@ Hp Printer Tech Support Phone Number Call wireless 1-800-784-6124 1-800- 784-6124 Hp Tech Support Phone Number Canada Hp printer customer service number1-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, hewlett packard support, Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, hewlett packard customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, hewlett packard printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, hewlett packard phone number, Hp printer customer service, Hp printer tech support number, Hp product support, hewlett packard customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support, hewlett packard tech support, Hp online chat, hewlett packard technical support, Hp printer help line, phone number for Hp support, hewlett packard support phone number, Hp printer technical support, hewlett packard customer service number, Hp service number, hewlett packard helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1800 number, Hp support phone, Hp support line, hewlett packard contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, hewlett packard support number, hewlett packard tech support number, Hp support telephone number, hewlett packard tech support phone number, call Hp, Hp contact support, hewlett packard technical support phone number, Hp support centre, hewlett packard customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, hewlett packard help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact hewlett packard by phone, Hp printer phone support, hewlett packard printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, hewlett packard customer service telephone number, phone number for hewlett packard, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, hewlett packard customer service phone, Hp laptop tech support, Hp service phone number, hewlett packard printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 800 number, hewlett packard technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact hewlett packard, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, hewlett packard telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, hewlett packard contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, hewlett packard printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, hewlett packard help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, hewlett packard support center, Hp laptop customer care no, Hp printer support telephone number, Hp support 1 800 247 1987 services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, hewlett packard customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, hewlett packard printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for hewlett packard customer service, hewlett packard 800 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 800 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, hewlett packard computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, contact Hp laptop support, Hp customer service contact number, support for Hp printer, Hp printer customer care no, 1 800 247 1987 Hp computer phone number, Hp tech help, Hp pc support number, Hp laptop customer support, Hp desktop support number, support Hp printer, Hp support hours, number for Hp support, Hp support customer service number, Hp contact phone number, customer service number for Hp printers, Hp computers help, Hp tech support contact number, Hp phone support Tech vew sUpP0RT.... Hp @PrinTer .1-800-7846124- .Support Phone Number,HP printer tech support number, HP Printer Customer Care Phone Number uSa. $UPP0RT.... Hp @PrinTer .1-800-784-6124- .Support Phone Number,Hp printer tech support number, Hp Printer Customer Care Phone Number uSa. HppRintERTEchSuppORtphOnENumbER1-800-784-6124HppRintERSuppORtphOnENumbER,HppRintERSuppORtNumbER,HppRintERtEchSuppORtNumbER..HppRintERssuppORtphOnEnumbER”-HppRintERsphOnEnumbER) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp pRintER tEch suppORt phOnE numbER usa canada Hp pRintER tEch suppORt phOnE numbER usa!!+++++1-800-784-6124+++Hp pRintER tEch suppORt phOnE numbER usa...pDF, Hp pRintER 1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,Hp pRintER tEchnical suppORt numbER1-800-784-6124 Hp pRintER custOmER sERvicE phOnE numbER,cannOn pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER,Hp 1-800-784-6124Hp pRintER hElplinE, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER tEch suppORt numbER 1-800-784-6124 Hp pRINTER tEch suppORt phOnE numbER USA !!Call aus 1-800-784-6124Hp TEch SuppORt phOnE NumbER UK-800-784-6124 Hp suppORt numbER, Hp suppORt, Hp pRintER suppORt, Hp tEch suppORt, Hp tEchnical suppORt, Hp custOmER sERvicE numbER, Hp custOmER sERvicE, Hp tEch suppORt numbER, Hp suppORt cEntER, Hp pRintER suppORt numbER, Hp suppORt suppORt, 1-800-784-6124 Hp cOntact numbER, Hp phOnE numbER, Hp hElp and suppORt, Hp custOmER suppORt, Hp pRintER hElp, Hp tEchnical suppORt numbER, Hp suppORt phOnE numbER, Hp suppORt custOmER sERvicE, Hp pRintERs suppORt, Hp custOmER sERvicE phOnE numbER, Hp numbER, Hp custOmER caRE, Hp cOntact, Hp tEch suppORt phOnE numbER, Hp suppORt chat, Hp custOmER suppORt numbER, Hp custOmER caRE numbER, cOntact Hp suppORt, Hp hElp, Hp phOnE, Hp pRintER suppORt phOnE numbER, Hp custOmER suppORt phOnE numbER, Hp pRintER tEch suppORt, Hp phOnE suppORt, Hp tEchnical suppORt phOnE numbER, Hp laptOp suppORt numbER, Hp suppORt pRintER suppORt, Hp hElplinE, Hp tElEphOnE suppORt, Hp OnlinE suppORt, Hp suppORt cOntact, Hp chat suppORt, Hp suppORt phOnE numbER, Hp pRintER custOmER sERvicE, Hp pRintER tEch suppORt numbER, Hp pROduct suppORt 1-800-784-6124 , Hp suppORt custOmER sERvicE phOnE numbER, Hp cOmputER suppORt numbER, Hp suppORt cOntact numbER, Hp suppORt pRintER, Hp cOmputER suppORt, Hp tEch suppORt chat, Hp hElplinE numbER, Hp laptOp suppORt1-800-784-6124, Hp suppORt tEch suppORt, Hp OnlinE chat, Hp suppORt tEchnical suppORt, Hp pRintER hElp linE, phOnE numbER fOR Hp suppORt, Hp suppORt suppORt phOnE numbER 1-800-784-6124, Hp pRintER tEchnical suppORt, Hp suppORt custOmER sERvicE numbER, Hp sERvicE numbER, Hp suppORt hElplinE, Hp custOmER caRE nO, Hp pRintER custOmER sERvicE numbER, Hp hElp numbER, Hp pRintER custOmER sERvicE phOnE numbER, Hp 1-800-784-6124 numbER, Hp suppORt phOnE, Hp suppORt linE, Hp suppORt cOntact numbER, Hp pRintER tEch suppORt phOnE numbER, Hp pRintER custOmER suppORt phOnE numbER, Hp pRintERs hElp, call Hp suppORt, Hp pRintER suppORt chat, Hp suppORt suppORt numbER, Hp suppORt tEch suppORt numbER, Hp suppORt tElEphOnE numbER, Hp suppORt tEch suppORt phOnE numbER, call Hp, Hp cOntact suppORt, Hp suppORt tEchnical suppORt phOnE numbER, Hp suppORt cEntRE, Hp suppORt custOmER suppORt, Hp dEsktOp suppORt, Hp laptOp custOmER sERvicE, cOntact Hp pRintER suppORt, Hp pc suppORt, Hp laptOp custOmER caRE numbER, Hp suppORt fOR pRintERs, Hp pRintER custOmER caRE, Hp custOmER caRE phOnE numbER, Hp suppORt hElp, phOnE numbER fOR Hp, Hp OnlinE hElp, Hp laptOp custOmER caRE, Hp hElplinE phOnE numbER, Hp pRintER custOmER suppORt, Hp tEchnical suppORt chat, Hp cOmputER hElp, Hp suppORt numbERs, Hp tEchnical suppORt cOntact numbER, Hp tElEphOnE numbER, Hp pRintER tEchnical suppORt phOnE numbER, Hp pRintER hElplinE, Hp suppORt pRintERs1-800-784-6124, Hp suppORt OnlinE, Hp pRintER cOntact numbER, Hp hElp phOnE numbER, Hp pRintER custOmER caRE numbER, cOntact Hp suppORt by phOnE, Hp pRintER phOnE suppORt, Hp suppORt pRintERs suppORt, Hp tEch suppORt phOnE, Hp tEchnical hElp, Hp laptOp tEch suppORt numbER, cOntact Hp by phOnE, Hp suppORt call, Hp cOmputERs suppORt, Hp suppORt custOmER sERvicE tElEphOnE numbER, phOnE numbER fOR Hp suppORt, Hp OnlinE suppORt chat, Hp laptOp custOmER sERvicE numbER, Hp OnlinE chat suppORt, Hp pRintERs custOmER sERvicE, Hp suppORt custOmER sERvicE phOnE, Hp laptOp tEch suppORt, Hp sERvicE phOnE numbER, Hp suppORt pRintER hElp, phOnE numbER fOR Hp pRintERs, Hp tROublEshOOting phOnE numbER, Hp 1-800-784-6124numbER, Hp suppORt tEchnical suppORt numbER, cOntact Hp suppORt phOnE, phOnE numbER fOR Hp pRintER suppORt, Hp custOmER suppORt chat, Hp hElp and suppORt numbER, cOntact Hp suppORt, Hp laptOp suppORt phOnE numbER, Hp pRintERs custOmER sERvicE phOnE numbER, Hp laptOp custOmER sERvicE phOnE numbER, Hp cOmputER suppORt phOnE numbER, Hp paviliOn suppORt, Hp cOmputER custOmER sERvicE, Hp custOmER sERvicEs, Hp suppORt tElEphOnE numbER, Hp hElplinE nO, Hp hElp dEsk numbER, cOntact Hp suppORt phOnE numbER, Hp suppORt cOntact, Hp phOnE numbERs, Hp pRintERs custOmER caRE numbER, Hp pRintER hElp and suppORt, cOntact Hp tEchnical suppORt, Hp cOntact numbERs, cOntact Hp suppORt chat, call Hp tEch suppORt, Hp custOmER sERvicE phOnE, Hp hElp suppORt, Hp cOmputER tEch suppORt, Hp assistancE phOnE numbER, Hp custOmER sERvicE tElEphOnE numbER, Hp suppORt pRintER suppORt phOnE numbER, Hp cOntact suppORt numbER, Hp suppORt cEntER phOnE numbER, Hp suppORt phOnE numbERs, tEch suppORt fOR Hp, Hp it suppORt, Hp laptOp hElplinE, Hp tEchnical, Hp laptOp tEchnical suppORt numbER, Hp pRintERs tEch suppORt phOnE numbER, Hp pRintERs suppORt phOnE numbER, Hp suppORt hElp dEsk phOnE numbER, Hp cOmputER tEch suppORt phOnE numbER, Hp custOmER sERvicE numbER fOR laptOp, Hp pRintER hElplinE numbER, cOntact Hp suppORt by phOnE, Hp suppORt suppORt cEntER, Hp laptOp custOmER caRE nO, Hp pRintER suppORt tElEphOnE numbER, Hp suppORt sERvicEs, Hp custOmER sERvicE numbER fOR pRintERs, Hp pROduct suppORt numbER, Hp laptOp tEch suppORt phOnE numbER, Hp pRintER hElplinE phOnE numbER, cOntact Hp custOmER suppORt, Hp suppORt custOmER suppORt phOnE numbER, Hp pRintERs tEchnical suppORt, Hp custOmER caRE cEntER, suppORt fOR Hp pRintERs, Hp pRintER suppORt cEntER, phOnE numbER fOR Hp tEch suppORt, Hp dEsktOp custOmER caRE numbER, Hp laptOps suppORt, Hp pRintER OnlinE suppORt, Hp pRintER phOnE numbER, Hp suppORt pRintERs suppORt phOnE numbER, tEchnical suppORt fOR Hp pRintERs phOnE numbER, Hp hElp cEntER phOnE numbER, cOntact Hp tEch suppORt, call Hp pRintER suppORt, Hp pRintERs custOmER suppORt, Hp cOmputER custOmER sERvicE numbER, Hp pRintERs hElplinE, Hp custOmER caRE cOntact numbER, Hp laptOp hElp, Hp cOmputER custOmER sERvicE phOnE numbER, phOnE numbER fOR Hp suppORt custOmER sERvicE, Hp suppORt 1-800-784-6124 numbER, Hp pRintER hElp phOnE numbER, Hp pRintERs hElp phOnE numbER, Hp pRintER phOnE numbER fOR custOmER sERvicE, Hp cOmputER tEchnical suppORt phOnE numbER, custOmER sERvicE Hp, Hp suppORt tEchnical suppORt numbER, cOntact numbER fOR Hp, Hp cOmputERs suppORt phOnE numbER, Hp pRintERs suppORt numbER, Hp pRintER tEchnical suppORt numbER, cOntact Hp tEch suppORt by phOnE, Hp cOmputER custOmER caRE numbER, Hp pRintER 1-800-784-6124 numbER, call Hp custOmER sERvicE, Hp pRintER hElp cEntER, Hp cOmputERs custOmER sERvicE, Hp pRintER hElp dEsk, Hp suppORt cOmputER suppORt, Hp pRintERs tEchnical suppORt numbER, Hp hElp dEsk phOnE numbER, Hp pRintER suppORt phOnE, Hp cOntact hElp, cOntact Hp laptOp suppORt, Hp custOmER sERvicE cOntact numbER, suppORt fOR Hp pRintER, Hp pRintER custOmER caRE nO, Hp cOmputER phOnE numbER, Hp tEch hElp, Hp pc suppORt numbER, Hp laptOp custOmER suppORt, Hp dEsktOp suppORt numbER, suppORt Hp pRintER, Hp suppORt hOuRs, numbER fOR Hp suppORt, Hp suppORt custOmER sERvicE numbER, Hp cOntact phOnE numbER, custOmER sERvicE numbER fOR Hp pRintERs, Hp cOmputERs hElp, Hp tEch suppORt cOntact numbER, Hp phOnE suppORt numbER Most Urgent 1 800 784 6124 Hp printer support phone number hp printer customer care phone number HpPRinterTechSupportPhoneNumber1-800-784 6124HpPrinterSupportPhoneNumber,HpPrinterSupportNumber,HpPrintertechSupportNumber..HpPrinterssupportphonenumber”-HpPrintersphonenumber) !!!UsA!!+++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada !!!UsA!!+++++((!!!!(1-800-784-6124))))))+++Hp printer tech support phone number usa canada Hp printer tech support phone number usa!!+++++1-800-784-6124+++Hp printer tech support phone number usa...PDF, Hp printer 1-800-784-6124 Hp printer customer service phone number,Hp printer technical support number1-800-784-6124 Hp printer customer service phone number,cannon printer helpline, Hp printer technical support phone number, Hp printer tech support number,Hp 1-800-784-6124Hp printer helpline, Hp printer technical support phone number, Hp printer tech support number 1-800-784-6124 Hp PRINTER tech support phone number USA !!Call aus 1-800-784-6124Hp Tech Support Phone Number UK-800-784-6124 Hp support number, Hp support, Hp printer support, Hp tech support, Hp technical support, Hp customer service number, Hp customer service, Hp tech support number, Hp support center, Hp printer support number, Hp support support, 1-800-784-6124 Hp contact number, Hp phone number, Hp help and support, Hp customer support, Hp printer help, Hp technical support number, Hp support phone number, Hp support customer service, Hp printers support, Hp customer service phone number, Hp number, Hp customer care, Hp contact, Hp tech support phone number, Hp support chat, Hp customer support number, Hp customer care number, contact Hp support, Hp help, Hp phone, Hp printer support phone number, Hp customer support phone number, Hp printer tech support, Hp phone support, Hp technical support phone number, Hp laptop support number, Hp support printer support, Hp helpline, Hp telephone support, Hp online support, Hp support contact, Hp chat support, Hp support phone number, Hp printer customer service, Hp printer tech support number, Hp product support 1-800-784-6124 , Hp support customer service phone number, Hp computer support number, Hp support contact number, Hp support printer, Hp computer support, Hp tech support chat, Hp helpline number, Hp laptop support1-800-784-6124, Hp support tech support, Hp online chat, Hp support technical support, Hp printer help line, phone number for Hp support, Hp support support phone number 1-800-784-6124, Hp printer technical support, Hp support customer service number, Hp service number, Hp support helpline, Hp customer care no, Hp printer customer service number, Hp help number, Hp printer customer service phone number, Hp 1-800-784-6124 number, Hp support phone, Hp support line, Hp support contact number, Hp printer tech support phone number, Hp printer customer support phone number, Hp printers help, call Hp support, Hp printer support chat, Hp support support number, Hp support tech support number, Hp support telephone number, Hp support tech support phone number, call Hp, Hp contact support, Hp support technical support phone number, Hp support centre, Hp support customer support, Hp desktop support, Hp laptop customer service, contact Hp printer support, Hp pc support, Hp laptop customer care number, Hp support for printers, Hp printer customer care, Hp customer care phone number, Hp support help, phone number for Hp, Hp online help, Hp laptop customer care, Hp helpline phone number, Hp printer customer support, Hp technical support chat, Hp computer help, Hp support numbers, Hp technical support contact number, Hp telephone number, Hp printer technical support phone number, Hp printer helpline, Hp support printers1-800-784-6124, Hp support online, Hp printer contact number, Hp help phone number, Hp printer customer care number, contact Hp support by phone, Hp printer phone support, Hp support printers support, Hp tech support phone, Hp technical help, Hp laptop tech support number, contact Hp by phone, Hp support call, Hp computers support, Hp support customer service telephone number, phone number for Hp support, Hp online support chat, Hp laptop customer service number, Hp online chat support, Hp printers customer service, Hp support customer service phone, Hp laptop tech support, Hp service phone number, Hp support printer help, phone number for Hp printers, Hp troubleshooting phone number, Hp 1-800-784-6124number, Hp support technical support number, contact Hp support phone, phone number for Hp printer support, Hp customer support chat, Hp help and support number, contact Hp support, Hp laptop support phone number, Hp printers customer service phone number, Hp laptop customer service phone number, Hp computer support phone number, Hp pavilion support, Hp computer customer service, Hp customer services, Hp support telephone number, Hp helpline no, Hp help desk number, contact Hp support phone number, Hp support contact, Hp phone numbers, Hp printers customer care number, Hp printer help and support, contact Hp technical support, Hp contact numbers, contact Hp support chat, call Hp tech support, Hp customer service phone, Hp help support, Hp computer tech support, Hp assistance phone number, Hp customer service telephone number, Hp support printer support phone number, Hp contact support number, Hp support center phone number, Hp support phone numbers, tech support for Hp, Hp it support, Hp laptop helpline, Hp technical, Hp laptop technical support number, Hp printers tech support phone number, Hp printers support phone number, Hp support help desk phone number, Hp computer tech support phone number, Hp customer service number for laptop, Hp printer helpline number, contact Hp support by phone, Hp support support center, Hp laptop customer care no, Hp printer support telephone number, Hp support services, Hp customer service number for printers, Hp product support number, Hp laptop tech support phone number, Hp printer helpline phone number, contact Hp customer support, Hp support customer support phone number, Hp printers technical support, Hp customer care center, support for Hp printers, Hp printer support center, phone number for Hp tech support, Hp desktop customer care number, Hp laptops support, Hp printer online support, Hp printer phone number, Hp support printers support phone number, technical support for Hp printers phone number, Hp help center phone number, contact Hp tech support, call Hp printer support, Hp printers customer support, Hp computer customer service number, Hp printers helpline, Hp customer care contact number, Hp laptop help, Hp computer customer service phone number, phone number for Hp support customer service, Hp support 1-800-784-6124 number, Hp printer help phone number, Hp printers help phone number, Hp printer phone number for customer service, Hp computer technical support phone number, customer service Hp, Hp support technical support number, contact number for Hp, Hp computers support phone number, Hp printers support number, Hp printer technical support number, contact Hp tech support by phone, Hp computer customer care number, Hp printer 1-800-784-6124 number, call Hp customer service, Hp printer help center, Hp computers customer service, Hp printer help desk, Hp support computer support, Hp printers technical support number, Hp help desk phone number, Hp printer support phone, Hp contact help, • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST • SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ • EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON FACEBOOK SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON TWITTER SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON PINTEREST SHARE “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER CUSTOMER SERVICE PHONE NUMBER HP PRINTER PHONE NUMBER” ON GOOGLE+ EMAIL “CUSTOMER )(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHON
Files
Filter
NameModified
(1800(.784 6124 HP LIVE SUPPORT HP PRINTER TECHNICAL SUPPORT PHONE NUMBER HP PRINTER
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7066) Wrong description of simple-regex-realm-mapper / mapped-regex-realm-mapper in model
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7066?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7066:
-----------------------------------
Fix Version/s: 11.0.0.Alpha1
> Wrong description of simple-regex-realm-mapper / mapped-regex-realm-mapper in model
> -----------------------------------------------------------------------------------
>
> Key: WFLY-7066
> URL: https://issues.jboss.org/browse/WFLY-7066
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Fix For: 11.0.0.Alpha1
>
>
> In output of {noformat}/subsystem=elytron:read-resource-description(recursive=true){noformat} , there is wrong description of simple-regex-realm-mapper / mapped-regex-realm-mapper _"Definition of a custom RealmMapper"_ , what is probably copied from custom-realm-mapper.
> In XSD, there is more proper
> * mapped-regex-realm-mapper: _"A RealmMapper implementaion that first uses a regular expression to extract the realm name, this is then converted using the configured mapping of realm names."_
> * simple-regex-realm-mapper: _"A simple RealmMapper definition that attempts to extract the realm name using the capture group from the regular expression, if that does not provide a match then the delegate RealmMapper is used instead."_
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7065) Wrong description of logical-role-mapper in model
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7065?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7065:
-----------------------------------
Fix Version/s: 11.0.0.Alpha1
> Wrong description of logical-role-mapper in model
> -------------------------------------------------
>
> Key: WFLY-7065
> URL: https://issues.jboss.org/browse/WFLY-7065
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Fix For: 11.0.0.Alpha1
>
>
> In output of
> {noformat}
> /subsystem=elytron:read-resource-description(recursive=true)
> {noformat}
> , there is wrong description of logical-role-mapper _A role mapper definition where a constant set of roles is always returned._ , what is probably copied from constant-role-mapper.
> In XSD, there is more proper description _A RoleMapper definition for a RoleMapper that performs a logical operation using two refereced RoleMappers._
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7075) proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-7075?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-7075:
-------------------------------
Summary: proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped (was: proposal (Extension): Adding ability of check testForMixedSynchronizationTypes by isJoinToTransaction (as current state of synchronization))
> proposal (Extension): allow checking of mixed persistence context synchronization types to be skipped
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-7075
> URL: https://issues.jboss.org/browse/WFLY-7075
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: *AppServer:* WildFly 10.1.0.Final
> *WildFly-jpa:* wildfly-jpa-10.1.0.Final.jar
> Reporter: Viacheslav Astapkovich
> Assignee: Scott Marlow
> Attachments: kitchensink-ear.rar
>
>
> As we mentioned in https://issues.jboss.org/browse/WFLY-6127 we found bug and made our solution.
>
> *The obtained defect:*
> A defect related to the check of synchronization type (to satisfy JPA spec 2.1 section 7.6.4.1) was found in WildFly 10.1.0.Final.
> The Method getSynchronizationType of class ExtendedEntityManager ALWAYS returns type of synchronization as SYNCHRONIZED (jar file: wildfly-jpa-10.1.0.Final.jar)
> *FIX:*
> We made a fork of WildFly-jpa project at: https://github.com/argustelecom/wildfly/tree/WFLY-6127
> Our Fix commit: https://github.com/wildfly/wildfly/commit/3bff5fde3cfc23f3999dc75c320029e...
> _Changes_: The method getSynchronizationType returns declared synchronization type.
> [WFLY-7108] is now the tracking jira for the fix.
> *Consequences:*
> We use own realisation of Martin Fowler pattern "Unit of Work". We initialize UNSYNCHRONIZED Extended Persistence Context and our UnitOfWork realisation manages the synchronization with transaction.
> Our Beans could be controlled by UnitOfWork, but also could be used as part of WebService call.
> It requires a declaration of synchronize persistence context.
> We catch IllegalStateException after we fixed defect of synchronization type determination, because we initialize UNSYNCHRONIZED persistence context, but we use declare SYNCHRONIZED persistence context in our beans.
> However, our UnitOfWork realisation control synchronization of persistence context and we can synchronize context before synchronization type check.
> *Our actions:*
> We add ability to check synchronization type in the method testForMixedSynchronizationTypes of class TransactionScopedEntityManager by isJoinToTransaction method (i.e. the actual type of synchronization).
> This ability realized by property "jboss.as.jpa.syncasjoin" in persistence.xml file. Only if this property setted to true - we perform testForMixedSynchronizationTypes by isJoinToTransaction method. We work as usual if this property not defined or setted to false.
> _Commit_: https://github.com/wildfly/wildfly/commit/195a8a65a9fae006ad603e425f6a16d...
> *Example for reproduction:*
> I modified quickstart example: [^kitchensink-ear.rar]
> MemberRepository begin Extended UNSYNCHRONIZED Persistence Context.
> MemberFinder.find called from MemberRepository. MemberFinder declared "SYNCHRONIZED", but MemberRepository declared UNSYNCHRONIZED.
> MemberRepository also perform join Transaction.
> Questions from [~smarlow]:
> - whether you could instead use an application-managed entity manager instead (which is similar to extended persistence context except the app controls it.
> We decided to use Container-managed EntityManager, because
> - Application-managed entity managers don’t automatically propagate the JTA transaction context. With application-managed entity managers the persistence context is not propagated to application components
> - The container makes our job
> We want to use the existing mechanism
> *In Addition:*
> Formally, this is out of JPA SPEC, but we have the following reasons:
> - In the development process of the JPA specification got a question: "Should we relax this if the PC has been joined to the transaction?".
> But unfortunately, Linda DeMichiel decided to leave as current behavior because no feedback was given.
> ( https://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2011-08/m... )
> - We found JIRA task https://java.net/jira/browse/JPA_SPEC-6 but it was closed because "No feedback in favor of changing current approach"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7127) CMR collection gets corrupted in 2LC on certain concurrent access
by Jari Juslin (JIRA)
Jari Juslin created WFLY-7127:
---------------------------------
Summary: CMR collection gets corrupted in 2LC on certain concurrent access
Key: WFLY-7127
URL: https://issues.jboss.org/browse/WFLY-7127
Project: WildFly
Issue Type: Bug
Components: EJB, JPA / Hibernate, Transactions
Affects Versions: 10.1.0.Final
Environment: Ubuntu Linux 15.10. Java 1.8.0_66
Reporter: Jari Juslin
Assignee: Scott Marlow
Attachments: infinispan_cmr_corruption_repro.tar.gz, standalone.xml
With certain parallel read and write access to same CMR collection it gets corrupted in Hibernate second level cache. After the event of corruption, any read access to that CMR collection ends up in Exception until the cache is cleared manually or Wildfly restarted.
Steps to reproduce:
1) Make sure the CMR collection is not in cache.
2) Start a read-only transaction accessing the said collection.
3) In a separate transaction delete an element from that collection.
4) End the read-only transaction.
5) Read the resulting collection. It now throws EntityNotFoundException.
My understanding is that what happens is that the read-only transaction is read-only from the perspective of the database, so the system handles it as such. However, because for the 2LC it is actually a write transaction, when the transaction ends, the contents of the CMR collection visible to this transaction get committed to 2LC. If the write transaction ends before the read-only transaction, the old version of the collection stays in the 2LC.
Now, as the CMR collection contains an element already deleted from the DB, any attempt to manifest the collection results in EntityNotFoundException as the child element no longer exists in the DB.
For sake of repeatibility the test case here manually spawns threads to cause the effect. In real use, of course, this happens randomly when two different threads spawned by Wildfly happen to interleave with exactly a right kind of pattern.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7126) No log messages comming from Elytron
by Josef Cacek (JIRA)
Josef Cacek created WFLY-7126:
---------------------------------
Summary: No log messages comming from Elytron
Key: WFLY-7126
URL: https://issues.jboss.org/browse/WFLY-7126
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Josef Cacek
Assignee: Darran Lofthouse
Priority: Critical
Elytron functionality is not covered (sufficiently) by log messages.
The log messages are cornerstone for customers when they're investigating configuration or functional issues.
Even when enabling {{TRACE}} log-level I was seeing No log messages coming from Elytron when I was configuring web authentication. When authentication fails it's not clear what's wrong - if password is invalid or permission mapper doesn't work or something else happened.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1804) CLI comments are not ended at the end of line
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1804?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-1804:
----------------------------------------------
This is an Aesh behavior. Aesh expects quotes and double quotes to be escaped: # test \" <return> works fine.
> CLI comments are not ended at the end of line
> ---------------------------------------------
>
> Key: WFCORE-1804
> URL: https://issues.jboss.org/browse/WFCORE-1804
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Alexey Loubyansky
> Assignee: Jean-Francois Denise
>
> *Description of problem:*
> * CLI comments are not ended at the end of line, if it contains quotation marks or apostrophes.
> * This is regression against EAP 6.4.x
> *How reproducible:*
> Always
> *Steps to Reproduce + Actual results:*
> {noformat}
> [standalone@localhost:9990 /] # test ' test
> >
> {noformat}
> {noformat}
> [standalone@localhost:9990 /] # what " what
> >
> {noformat}
> *Expected results:*
> {noformat}
> [standalone@localhost:9990 /] # test ' test
> [standalone@localhost:9990 /]
> {noformat}
> {noformat}
> [standalone@localhost:9990 /] # what " what
> [standalone@localhost:9990 /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7125) Required attributes of elytron key-store creation CLI command
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7125?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFLY-7125:
-------------------------------
Description:
Minimal CLI command to create key store is
{code}
/subsystem=elytron/key-store=server:add(type="JKS")
{code}
But it has these problems:
* Password attribute has to be required. I can't think of case when that could be ommited.
* Attribute {{type}} could be optional. If not set default value can be Keystore.getDefaultType(). As model cant't express this, it can be documented in description.
was:
Minimal CLI command to create key store is
{code}
/subsystem=elytron/key-store=server:add(type="JKS")
{code}
But it has these problems:
* Command let me create jks keystore without {{path}} specified. It is because {{required}} attribute is default to false. I can think of 2 {{required=false}} usages:
PKCS11
some sort of dynamic key-store creation in runtime
But that looks to me as less common cases. I think dominantlly user will use file-based key store type with existing keystore. So I would propose to change default {{required}} default to true.
* Password attribute has to be required. I can't think of case when that could be ommited.
* Attribute {{type}} could be optional. If not set default value can be Keystore.getDefaultType(). As model cant't express this, it can be documented in description.
In result it will be possible to create key-store by this minimal CLI command:
{code}
/subsystem=elytron/key-store=server:add(path="server.jks", password="secret")
{code}
> Required attributes of elytron key-store creation CLI command
> -------------------------------------------------------------
>
> Key: WFLY-7125
> URL: https://issues.jboss.org/browse/WFLY-7125
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Critical
>
> Minimal CLI command to create key store is
> {code}
> /subsystem=elytron/key-store=server:add(type="JKS")
> {code}
> But it has these problems:
> * Password attribute has to be required. I can't think of case when that could be ommited.
> * Attribute {{type}} could be optional. If not set default value can be Keystore.getDefaultType(). As model cant't express this, it can be documented in description.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1804) CLI comments are not ended at the end of line
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1804?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky reassigned WFCORE-1804:
-----------------------------------------
Assignee: Jean-Francois Denise (was: Alexey Loubyansky)
Jeff, could you please investigate? Thanks!
> CLI comments are not ended at the end of line
> ---------------------------------------------
>
> Key: WFCORE-1804
> URL: https://issues.jboss.org/browse/WFCORE-1804
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Alexey Loubyansky
> Assignee: Jean-Francois Denise
>
> *Description of problem:*
> * CLI comments are not ended at the end of line, if it contains quotation marks or apostrophes.
> * This is regression against EAP 6.4.x
> *How reproducible:*
> Always
> *Steps to Reproduce + Actual results:*
> {noformat}
> [standalone@localhost:9990 /] # test ' test
> >
> {noformat}
> {noformat}
> [standalone@localhost:9990 /] # what " what
> >
> {noformat}
> *Expected results:*
> {noformat}
> [standalone@localhost:9990 /] # test ' test
> [standalone@localhost:9990 /]
> {noformat}
> {noformat}
> [standalone@localhost:9990 /] # what " what
> [standalone@localhost:9990 /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1804) CLI comments are not ended at the end of line
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1804?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky moved JBEAP-6038 to WFCORE-1804:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1804 (was: JBEAP-6038)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
> CLI comments are not ended at the end of line
> ---------------------------------------------
>
> Key: WFCORE-1804
> URL: https://issues.jboss.org/browse/WFCORE-1804
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
>
> *Description of problem:*
> * CLI comments are not ended at the end of line, if it contains quotation marks or apostrophes.
> * This is regression against EAP 6.4.x
> *How reproducible:*
> Always
> *Steps to Reproduce + Actual results:*
> {noformat}
> [standalone@localhost:9990 /] # test ' test
> >
> {noformat}
> {noformat}
> [standalone@localhost:9990 /] # what " what
> >
> {noformat}
> *Expected results:*
> {noformat}
> [standalone@localhost:9990 /] # test ' test
> [standalone@localhost:9990 /]
> {noformat}
> {noformat}
> [standalone@localhost:9990 /] # what " what
> [standalone@localhost:9990 /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-630) Elytron - aggregate-role-mapper can contain multi reference to one role mapper
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-630?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse commented on ELY-630:
--------------------------------------
As I have mentioned elsewhere I don't think this is necessarily an invalid configuration - as administrators can plug in custom implementations there is always a possibility that they may want their implementation repeating.
> Elytron - aggregate-role-mapper can contain multi reference to one role mapper
> ------------------------------------------------------------------------------
>
> Key: ELY-630
> URL: https://issues.jboss.org/browse/ELY-630
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Priority: Minor
>
> Aggregate-role-mapper can contain multi reference to one role mapper.
> In my opinion it isn't valid state.
> But there is some probability that it is required behaviour.
> Can you have a look on it?
> Configuration snippet:
> {code}
> <subsystem xmlns="urn:wildfly:elytron:1.0">
> <mappers>
> <add-prefix-role-mapper name="CreaperTestAddPrefixRoleMapper" prefix="somePrefix"/>
> <aggregate-role-mapper name="CreaperTestAggregateRoleMapper">
> <role-mapper name="CreaperTestAddPrefixRoleMapper"/>
> <role-mapper name="CreaperTestAddPrefixRoleMapper"/>
> </aggregate-role-mapper>
> </mappers>
> </subsystem>
> {code}
> *Actual results:*
> Aggregate-role-mapper can contain multi reference to one role-mapper.
> *Expected results:*
> You would not be able to define multi reference to one role-mapper in aggregate-role-mapper.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-2640) Unable to add cached-connection-manager after removing it once
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/WFLY-2640?page=com.atlassian.jira.plugin.... ]
Ingo Weiss commented on WFLY-2640:
----------------------------------
I will take a look at this one
> Unable to add cached-connection-manager after removing it once
> --------------------------------------------------------------
>
> Key: WFLY-2640
> URL: https://issues.jboss.org/browse/WFLY-2640
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 8.0.0.Beta1
> Reporter: Masafumi Miura
>
> {{<cached-connection-manager>}} is enabled in jca subsystem by default:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:jca:1.1">
> ...
> <cached-connection-manager />
> </subsystem>
> {code}
> However, it is unable to re-enable {{<cached-connection-manager>}} once it is disabled. CLI command fails to add it due to duplicate resource.
> {code}
> [standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:remove
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> [standalone@localhost:9990 /] :reload
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:add
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014803: Duplicate resource [
> (\"subsystem\" => \"jca\"),
> (\"cached-connection-manager\" => \"cached-connection-manager\")
> ]",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7125) Required attributes of elytron key-store creation CLI command
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7125?page=com.atlassian.jira.plugin.... ]
Martin Choma moved JBEAP-6035 to WFLY-7125:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7125 (was: JBEAP-6035)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR4)
> Required attributes of elytron key-store creation CLI command
> -------------------------------------------------------------
>
> Key: WFLY-7125
> URL: https://issues.jboss.org/browse/WFLY-7125
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Critical
>
> Minimal CLI command to create key store is
> {code}
> /subsystem=elytron/key-store=server:add(type="JKS")
> {code}
> But it has these problems:
> * Command let me create jks keystore without {{path}} specified. It is because {{required}} attribute is default to false. I can think of 2 {{required=false}} usages:
> PKCS11
> some sort of dynamic key-store creation in runtime
> But that looks to me as less common cases. I think dominantlly user will use file-based key store type with existing keystore. So I would propose to change default {{required}} default to true.
> * Password attribute has to be required. I can't think of case when that could be ommited.
> * Attribute {{type}} could be optional. If not set default value can be Keystore.getDefaultType(). As model cant't express this, it can be documented in description.
> In result it will be possible to create key-store by this minimal CLI command:
> {code}
> /subsystem=elytron/key-store=server:add(path="server.jks", password="secret")
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-630) Elytron - aggregate-role-mapper can contain multi reference to one role mapper
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-630:
--------------------------------
Summary: Elytron - aggregate-role-mapper can contain multi reference to one role mapper
Key: ELY-630
URL: https://issues.jboss.org/browse/ELY-630
Project: WildFly Elytron
Issue Type: Bug
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Priority: Minor
Aggregate-role-mapper can contain multi reference to one role mapper.
In my opinion it isn't valid state.
But there is some probability that it is required behaviour.
Can you have a look on it?
Configuration snippet:
{code}
<subsystem xmlns="urn:wildfly:elytron:1.0">
<mappers>
<add-prefix-role-mapper name="CreaperTestAddPrefixRoleMapper" prefix="somePrefix"/>
<aggregate-role-mapper name="CreaperTestAggregateRoleMapper">
<role-mapper name="CreaperTestAddPrefixRoleMapper"/>
<role-mapper name="CreaperTestAddPrefixRoleMapper"/>
</aggregate-role-mapper>
</mappers>
</subsystem>
{code}
*Actual results:*
Aggregate-role-mapper can contain multi reference to one role-mapper.
*Expected results:*
You would not be able to define multi reference to one role-mapper in aggregate-role-mapper.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1279) [GSS] compilation of spreadsheet fails with specific condition
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1279?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-1279:
--------------------------------------
Assignee: Michael Anstis (was: Petr Široký)
> [GSS] compilation of spreadsheet fails with specific condition
> --------------------------------------------------------------
>
> Key: DROOLS-1279
> URL: https://issues.jboss.org/browse/DROOLS-1279
> Project: Drools
> Issue Type: Bug
> Components: build, decision tables
> Affects Versions: 6.4.0.Final
> Reporter: Hiroko Miura
> Assignee: Michael Anstis
> Priority: Critical
> Labels: support
> Fix For: 6.5.0.Final
>
> Attachments: reproducer.zip
>
>
> Reproducer is attached.with problematic spredsheet named SampleNG.xml.
> Compilation of this fails with the following error.
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=dtables/SampleNG.xls, line=8, column=0
> text=Unable to Analyse Expression checktest == AAA:
> [Error: unable to resolve method using strict-mode: com.sample.DecisionTableTest$Message.AAA()]
> [Near : {... checktest == AAA ....}]
> because the following DRL is generated.
> rule "HelloWorld_12"
> when
> m:Message(checktest in (AAA), status == "Message.HELLO")
> ...
> i.e. double quotation of value ("AAA") specified in the cell is removed.
>
> If D column does not exist like Sample.xml(also included in reproducer) or rule template of D column is modified like "status == $param " (see SampleOK.xml), this does not happen.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1250) Drools Sample.drl is broken
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1250?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky resolved DROOLS-1250.
---------------------------------------
Fix Version/s: 6.5.0.Final
Resolution: Done
Hi [~bbrodt], please let this issue as RESOLVED. QE will close it once the fix is included in a product, e.g. JBDS-IS.
(please note that QE uses the Jira states in tests so that we can in some cases skip the tests which are supposed to fail)
> Drools Sample.drl is broken
> ---------------------------
>
> Key: DROOLS-1250
> URL: https://issues.jboss.org/browse/DROOLS-1250
> Project: Drools
> Issue Type: Feature Request
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Reporter: Tianwei Chen
> Assignee: Robert (Bob) Brodt
> Fix For: 6.5.0.Final
>
>
> Hello, I use drools plugin (6.4.0.Final) in Eclipse Neon. I followed the wizard to create a drools project with some example files. After the step were done, Eclipse highlighted errors at the two rules in the Sample.drl file. Here is one of the errors:
> Multiple markers at this line
> - com.sample.DroolsTest.Message cannot be resolved to a type
> - org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> - Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> - org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> - KnowledgeHelper cannot be resolved to a type
> - Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> - Message.GOODBYE cannot be resolved to a type
> - org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> - java.lang.Exception cannot be resolved to a type
> When I ran DroolsTest.java, I got the following error:
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=Sample.drl, line=15, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type], Message [id=2, level=ERROR, path=Sample.drl, line=5, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type]]
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:450)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:604)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:575)
> It seems like an library path issue. Please help!
> Thank you very much!
> Tianwei Chen
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1250) Drools Sample.drl is broken
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1250?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky reopened DROOLS-1250:
---------------------------------------
Reopened just to set correct state
> Drools Sample.drl is broken
> ---------------------------
>
> Key: DROOLS-1250
> URL: https://issues.jboss.org/browse/DROOLS-1250
> Project: Drools
> Issue Type: Feature Request
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Reporter: Tianwei Chen
> Assignee: Robert (Bob) Brodt
>
> Hello, I use drools plugin (6.4.0.Final) in Eclipse Neon. I followed the wizard to create a drools project with some example files. After the step were done, Eclipse highlighted errors at the two rules in the Sample.drl file. Here is one of the errors:
> Multiple markers at this line
> - com.sample.DroolsTest.Message cannot be resolved to a type
> - org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> - Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> - org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> - KnowledgeHelper cannot be resolved to a type
> - Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> - Message.GOODBYE cannot be resolved to a type
> - org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> - java.lang.Exception cannot be resolved to a type
> When I ran DroolsTest.java, I got the following error:
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=Sample.drl, line=15, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type], Message [id=2, level=ERROR, path=Sample.drl, line=5, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type]]
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:450)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:604)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:575)
> It seems like an library path issue. Please help!
> Thank you very much!
> Tianwei Chen
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1716) JMX domains jboss.as and jboss.as.expr do not always correctly handle propertly list patters in queryMBeans and queryNames
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1716?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on WFCORE-1716:
-------------------------------------------------
Radovan Netuka <rnetuka(a)redhat.com> changed the Status of [bug 1367784|https://bugzilla.redhat.com/show_bug.cgi?id=1367784] from ASSIGNED to POST
> JMX domains jboss.as and jboss.as.expr do not always correctly handle propertly list patters in queryMBeans and queryNames
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1716
> URL: https://issues.jboss.org/browse/WFCORE-1716
> Project: WildFly Core
> Issue Type: Bug
> Components: JMX
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 3.0.0.Alpha6
>
>
> The ObjectName filtering logic added for WFLY-3161 does not handle queryMBeans and queryNames correctly in some cases where the ObjectName param to the method is a property list pattern (i.e. one that includes a simple '*' at the end of the list of properties, meaning "all other properties besides previous ones whose keys were specifically enumerated, match".)
> The problem occurs when the the ObjectName does specifically include some keys, and those keys don't correspond to the final elements of the related management resource's PathAddress. As the RootResourceIterator walks the management resource tree, ModelControllerMBeanHelper.ObjectNameMatchResourceAction will not identify the parent resources of children that should match as matching, with the result that the iterator will not descend into that part of the tree and the children will not be matched. For example, this query will return an empty set because the /socket-binding-group=standard-sockets parent will not be matched, preventing checks of the socket-binding-group children.
> {code}
> Set<ObjectInstance> instances = connection.queryMBeans(createObjectName("jboss.as:socket-binding=*,*"), null);
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1279) [GSS] compilation of spreadsheet fails with specific condition
by Hiroko Miura (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1279?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-1279:
---------------------------------
Priority: Critical (was: Major)
> [GSS] compilation of spreadsheet fails with specific condition
> --------------------------------------------------------------
>
> Key: DROOLS-1279
> URL: https://issues.jboss.org/browse/DROOLS-1279
> Project: Drools
> Issue Type: Bug
> Components: build, decision tables
> Affects Versions: 6.4.0.Final
> Reporter: Hiroko Miura
> Assignee: Petr Široký
> Priority: Critical
> Labels: support
> Fix For: 6.5.0.Final
>
> Attachments: reproducer.zip
>
>
> Reproducer is attached.with problematic spredsheet named SampleNG.xml.
> Compilation of this fails with the following error.
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=dtables/SampleNG.xls, line=8, column=0
> text=Unable to Analyse Expression checktest == AAA:
> [Error: unable to resolve method using strict-mode: com.sample.DecisionTableTest$Message.AAA()]
> [Near : {... checktest == AAA ....}]
> because the following DRL is generated.
> rule "HelloWorld_12"
> when
> m:Message(checktest in (AAA), status == "Message.HELLO")
> ...
> i.e. double quotation of value ("AAA") specified in the cell is removed.
>
> If D column does not exist like Sample.xml(also included in reproducer) or rule template of D column is modified like "status == $param " (see SampleOK.xml), this does not happen.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7123) Use elytron ssl-context for undertow default https listener
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7123?page=com.atlassian.jira.plugin.... ]
Martin Choma moved JBEAP-6031 to WFLY-7123:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7123 (was: JBEAP-6031)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
Web (Undertow)
(was: Security)
(was: Web (Undertow))
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR4)
> Use elytron ssl-context for undertow default https listener
> -----------------------------------------------------------
>
> Key: WFLY-7123
> URL: https://issues.jboss.org/browse/WFLY-7123
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Stuart Douglas
> Priority: Blocker
>
> Default undertow https listener use legacy ssl context in standalone-elytron.xml .
> {code}
> <https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/>
> {code}
> Once elytron becomes default security solution in wildfly it has to use elytron ssl context. In meantime prepare such configuration in standalone-elytron.xml
> {code}
> <https-listener name="https" socket-binding="https" ssl-context="elytron-ssl-context" enable-http2="true"/>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1296) Root path of kjar module is incorrectly calculated under Windows for both spring and blueprint integration
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-1296:
-----------------------------------
Summary: Root path of kjar module is incorrectly calculated under Windows for both spring and blueprint integration
Key: DROOLS-1296
URL: https://issues.jboss.org/browse/DROOLS-1296
Project: Drools
Issue Type: Bug
Components: integration
Reporter: Mario Fusco
Assignee: Mario Fusco
Fix For: 7.0.0.Beta2
KModule post processor wherein createKieModule method implementation removes the drive name from the base directory url which causes the problem. So if we have base jetty temp dir path like C:\users\user\tem\jettytempfolder\webapp\web-inf\classes the below lines of code removes the "C:\" from the url which makes it invalid path and which in turn isnt recognized as classes file folder.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7122) Add configuration to disable systematic file watch in ServletResourceManager
by Stuart Douglas (JIRA)
Stuart Douglas created WFLY-7122:
------------------------------------
Summary: Add configuration to disable systematic file watch in ServletResourceManager
Key: WFLY-7122
URL: https://issues.jboss.org/browse/WFLY-7122
Project: WildFly
Issue Type: Feature Request
Components: Web (Undertow)
Affects Versions: 10.0.0.Final
Environment: Oracle JDK 8u74 on CentOs
Reporter: Mathieu Lachance
Assignee: Stuart Douglas
Our application is deployed multiple time in production as an exploded war.
Eventually we are running into "User limit of inotify watches reached":
{code}
ERROR [io.undertow] (MSC service thread 1-6) UT005024: Could not register resource change listener for caching resource manager, automatic invalidation of cached resource will not work: java.lang.RuntimeException: java.io.IOException: User limit of inotify watches reached
at org.xnio.nio.WatchServiceFileSystemWatcher.watchPath(WatchServiceFileSystemWatcher.java:179)
at io.undertow.server.handlers.resource.FileResourceManager.registerResourceChangeListener(FileResourceManager.java:161) [undertow-core-1.1.0.Final.jar:1.1.0.Final]
at org.wildfly.extension.undertow.deployment.ServletResourceManager.registerResourceChangeListener(ServletResourceManager.java:80)
at io.undertow.server.handlers.resource.CachingResourceManager.<init>(CachingResourceManager.java:64) [undertow-core-1.1.0.Final.jar:1.1.0.Final]
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:525)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:256)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]
Caused by: java.io.IOException: User limit of inotify watches reached
at sun.nio.fs.LinuxWatchService$Poller.implRegister(LinuxWatchService.java:264) [rt.jar:1.8.0_45]
at sun.nio.fs.AbstractPoller.processRequests(AbstractPoller.java:260) [rt.jar:1.8.0_45]
at sun.nio.fs.LinuxWatchService$Poller.run(LinuxWatchService.java:329) [rt.jar:1.8.0_45]
... 1 more
{code}
>From what I'm seeing in:
https://github.com/wildfly/wildfly/blob/master/undertow/src/main/java/org...
https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io...
https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io...
there's no way to disable the file resource watch at the sole exception of using non-exploded war deployment.
We will eventually switch to a non-exploded war but I think having a configuration (either within the standalone.xml or via system property) to completly turn off that feature would be a nice addition / improvement.
In the meanwhile, as a workaround we have increased the inotify watch on the OS and will most likely patch either undertow and/or wildfly-undertow to not add any watch at all.
Thanks
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1295) (6.5.x) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment
by Hiroko Miura (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1295?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-1295:
---------------------------------
Description:
This is cloned from DROOLS-1286 in order to back-port to Community 6.5.x branch.
Guided Decision Table: When adding a Condition BRL fragment it is not possible to enter a template key or value for an attribute on a domain object.
In the attached screen shot, when clicking pencil icon, nothing appear.
This is confirmed by both FireFox anc Chrome.
At that time, the following error is shown in browser's console.
[Chrome]
12:44:40 SEVERE [LogConfiguration] Exception caught: (TypeError) : Cannot read property 'indexOf' of null
[FireFox]
00:10:46 SEVERE [LogConfiguration] Exception caught: (TypeError) : b.indexOf is null
was:
Guided Decision Table: When adding a Condition BRL fragment it is not possible to enter a template key or value for an attribute on a domain object.
In the attached screen shot, when clicking pencil icon, nothing appear.
This is confirmed by both FireFox anc Chrome.
At that time, the following error is shown in browser's console.
[Chrome]
12:44:40 SEVERE [LogConfiguration] Exception caught: (TypeError) : Cannot read property 'indexOf' of null
[FireFox]
00:10:46 SEVERE [LogConfiguration] Exception caught: (TypeError) : b.indexOf is null
Fix Version/s: (was: 7.0.0.Beta2)
Affects Version/s: 6.5.0.CR2
> (6.5.x) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1295
> URL: https://issues.jboss.org/browse/DROOLS-1295
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 6.4.0.Final, 6.5.0.CR2
> Reporter: Hiroko Miura
> Assignee: Michael Anstis
> Labels: support
>
> This is cloned from DROOLS-1286 in order to back-port to Community 6.5.x branch.
> Guided Decision Table: When adding a Condition BRL fragment it is not possible to enter a template key or value for an attribute on a domain object.
> In the attached screen shot, when clicking pencil icon, nothing appear.
> This is confirmed by both FireFox anc Chrome.
> At that time, the following error is shown in browser's console.
> [Chrome]
> 12:44:40 SEVERE [LogConfiguration] Exception caught: (TypeError) : Cannot read property 'indexOf' of null
>
> [FireFox]
> 00:10:46 SEVERE [LogConfiguration] Exception caught: (TypeError) : b.indexOf is null
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1295) (6.5.x) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment
by Hiroko Miura (JIRA)
Hiroko Miura created DROOLS-1295:
------------------------------------
Summary: (6.5.x) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment
Key: DROOLS-1295
URL: https://issues.jboss.org/browse/DROOLS-1295
Project: Drools
Issue Type: Bug
Components: decision tables
Affects Versions: 6.4.0.Final
Reporter: Hiroko Miura
Assignee: Michael Anstis
Fix For: 7.0.0.Beta2
Guided Decision Table: When adding a Condition BRL fragment it is not possible to enter a template key or value for an attribute on a domain object.
In the attached screen shot, when clicking pencil icon, nothing appear.
This is confirmed by both FireFox anc Chrome.
At that time, the following error is shown in browser's console.
[Chrome]
12:44:40 SEVERE [LogConfiguration] Exception caught: (TypeError) : Cannot read property 'indexOf' of null
[FireFox]
00:10:46 SEVERE [LogConfiguration] Exception caught: (TypeError) : b.indexOf is null
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1719) Wildfly 10.1.0.CR1 does not start as a windows service
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1719?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1719:
-------------------------------------
Fix Version/s: 2.2.1.Final
> Wildfly 10.1.0.CR1 does not start as a windows service
> ------------------------------------------------------
>
> Key: WFCORE-1719
> URL: https://issues.jboss.org/browse/WFCORE-1719
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.2.0.Final
> Environment: Windows 8/Windows Server 2012
> Oracle Java 8
> Reporter: Anton Yudin
> Assignee: Tomaz Cerar
> Fix For: 3.0.0.Alpha6, 2.2.1.Final
>
>
> Wildfly fails to start as a windows service.
> Installation works fine:
> {code}
> .\service.bat install
> Using the X86-64bit version of prunsrv
> "C:\applications\wildfly-10.1.0.CR1-test\bin\service\amd64\wildfly-service" install Wildfly --DisplayName=WildFly --Description=""WildFly Application Server"" --LogLevel=INFO --LogPath="C:\applications\wildfly-10.1.0.CR1-test\standalone\log" --LogPrefix=service --StdOutput=auto --StdError=auto --StartMode=exe --Startup=manual --StartImage=cmd.exe --StartPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StartParams="/c#set#NOPAUSE=Y#&&#standalone.bat#-Djboss.server.base.dir=C:\applications\wildfly-10.1.0.CR1-test\standalone#--server-config=standalone.xml" --StopMode=exe --StopImage=cmd.exe --StopPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StopParams="/c jboss-cli.bat --controller=localhost:9990 --connect --command=:shutdown"
> Service Wildfly installed
> {code}
> Windows reports this error:
> {quote}
> Windows could not start the Wildfly on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1.
> {quote}
> {code}
> Event log report:
> The Wildfly service terminated with the following service-specific error:
> Incorrect function.
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager"/>
> <EventID Qualifiers="49152">7024</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x8080000000000000</Keywords>
> <TimeCreated SystemTime="2016-08-13T21:40:42.402218400Z"/>
> <EventRecordID>196500</EventRecordID>
> <Correlation/>
> <Execution ProcessID="668" ThreadID="10184"/>
> <Channel>System</Channel>
> <Computer>ITPC7.intra.rfgh.net</Computer>
> <Security/>
> </System>
> -
> <EventData>
> <Data Name="param1">Wildfly</Data>
> <Data Name="param2">%%1</Data>
> <Binary>570069006C00640066006C0079000000</Binary>
> </EventData>
> </Event>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1801) DomainSlaveHostRegistrations should survive a reload
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1801:
----------------------------------------
Summary: DomainSlaveHostRegistrations should survive a reload
Key: WFCORE-1801
URL: https://issues.jboss.org/browse/WFCORE-1801
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Priority: Minor
DomainSlaveHostRegistrations is used by the master to record HC registration/unregistration events for display via the management API. The lifecycle of this data is tied to that of DomainModelControllerService, which gets gc'd and recreated on each reload. This data should have a longer lifespan than that.
It doesn't need to be persistent (survive HC restart) but surviving reload would be better.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1294) Root path of kjar module is incorrectly calculated under Windows for both spring and blueprint integration
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1294?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-1294:
--------------------------------
Description: KModule post processor wherein createKieModule method implementation removes the drive name from the base directory url which causes the problem. So if we have base jetty temp dir path like C:\users\user\tem\jettytempfolder\webapp\web-inf\classes the below lines of code removes the "C:\" from the url which makes it invalid path and which in turn isnt recognized as classes file folder.
> Root path of kjar module is incorrectly calculated under Windows for both spring and blueprint integration
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1294
> URL: https://issues.jboss.org/browse/DROOLS-1294
> Project: Drools
> Issue Type: Bug
> Components: integration
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> KModule post processor wherein createKieModule method implementation removes the drive name from the base directory url which causes the problem. So if we have base jetty temp dir path like C:\users\user\tem\jettytempfolder\webapp\web-inf\classes the below lines of code removes the "C:\" from the url which makes it invalid path and which in turn isnt recognized as classes file folder.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-298) load-from/uri keystore xsd/parser mismatch
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-298?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-298:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> load-from/uri keystore xsd/parser mismatch
> ------------------------------------------
>
> Key: ELY-298
> URL: https://issues.jboss.org/browse/ELY-298
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Reporter: Kabir Khan
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta10
>
>
> The xsd has
> {code}
> <xsd:complexType name="key-store-type">
> <xsd:sequence minOccurs="1" maxOccurs="1">
> <!-- Access source type -->
> <xsd:choice minOccurs="1" maxOccurs="1">
> <xsd:element name="file" type="name-type" minOccurs="1" maxOccurs="1"/>
> <xsd:element name="load-from" type="uri-type" minOccurs="1" maxOccurs="1"/>
> <xsd:element name="resource" type="name-type" minOccurs="1" maxOccurs="1"/>
> {code}
> The parser seems to look for 'uri' rather than 'load-from'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-212) Client-side SSL context configuration is subtly wrong
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-212?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-212:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> Client-side SSL context configuration is subtly wrong
> -----------------------------------------------------
>
> Key: ELY-212
> URL: https://issues.jboss.org/browse/ELY-212
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.1.0.Beta10
>
>
> SSL context client-side configuration is problematic in that the SSL context is not (and cannot be) cached. This means that we lose SSL session reuse and other benefits which may cause problems for users.
> However we also cannot just cache an SSL context on a configuration either - the client credentials may vary on each request, causing leakage between identities.
> What we need to do is have a separate SSL context client configuration mechanism, and use the generic client context configuration to reference this SSL context client configuration.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-444) AuthorizationIdentity and PermissionMapper
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-444?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-444:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> AuthorizationIdentity and PermissionMapper
> ------------------------------------------
>
> Key: ELY-444
> URL: https://issues.jboss.org/browse/ELY-444
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: API / SPI, Realms
> Reporter: David Lloyd
> Fix For: 1.1.0.Beta10
>
>
> When we initially designed the PermissionMapper we went to certain lengths to avoid exposing details of the realm. But now as the API has evolved it is clear that the permission mapper will need access to more information. The AuthorizationIdentity (or perhaps another object which includes the AuthorizationIdentity) should be made available to the permission mapper.
> In addition, this object could be expanded to include more information about the authentication, for example mechanism-specific information, which can feed into the authorization decision and could be useful for other things. Examples include: authentication timestamp, mechanism name/kind, forwarding credentials, and other attributes which derive from the mechanism as opposed to the identity.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-509) Multi Step HTTP Authentication
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-509?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-509:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> Multi Step HTTP Authentication
> ------------------------------
>
> Key: ELY-509
> URL: https://issues.jboss.org/browse/ELY-509
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Farah Juma
> Fix For: 1.1.0.Beta10
>
>
> This is a variation of FORM authentication and closely related to ELY-508.
> The scenario would be prompt for a username, then prompt for a password and if the password is valid and the account supports OTP prompt for the OTP.
> The mechanism may also be responsible for sending the OTP but that is probably a side topic.
> I have raised this in terms of being a HTTP mechanism but the main point we need to ensure is covered is the requirements about identifying what checks are required for a specific user and tracking they are all complete.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-477) XmlConfigurationTest.testWrongRuleOrder fails with IBM JDK
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-477?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-477:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> XmlConfigurationTest.testWrongRuleOrder fails with IBM JDK
> ----------------------------------------------------------
>
> Key: ELY-477
> URL: https://issues.jboss.org/browse/ELY-477
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Testsuite
> Affects Versions: 1.1.0.Beta4
> Reporter: Ondrej Lukas
> Fix For: 1.1.0.Beta10
>
>
> Test XmlConfigurationTest.testWrongRuleOrder fails with IBM JDK with:
> {code}
> expected:<-1> but was:<7>
> and stacktrace:
> java.lang.AssertionError: expected:<-1> but was:<7>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.wildfly.security.auth.client.XmlConfigurationTest.testWrongRuleOrder(XmlConfigurationTest.java:96)
> ...
> {code}
> It is caused by undefined line number of XML parsing failure for IBM JDK.
> Stacktrace of checked XMLStreamException for IBM JDK:
> {code}
> org.wildfly.client.config.ConfigXMLParseException:
> CONF000005: Unexpected element "{urn:elytron:1.0}match-host" encountered
> at authentication-client.xml:
> at org.wildfly.client.config.ConfigurationXMLStreamReader.unexpectedElement(ConfigurationXMLStreamReader.java:257)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientRuleType(ElytronXmlParser.java:341)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientRulesType(ElytronXmlParser.java:238)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:181)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:118)
> at org.wildfly.security.auth.client.XmlConfigurationTest.testWrongRuleOrder(XmlConfigurationTest.java:93)
> ...
> {code}
> Stacktrace of checked XMLStreamException for Oracle JDK:
> {code}
> org.wildfly.client.config.ConfigXMLParseException:
> CONF000005: Unexpected element "{urn:elytron:1.0}match-host" encountered
> at authentication-client.xml:7:39:
> at org.wildfly.client.config.ConfigurationXMLStreamReader.unexpectedElement(ConfigurationXMLStreamReader.java:257)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientRuleType(ElytronXmlParser.java:341)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientRulesType(ElytronXmlParser.java:238)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:181)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:118)
> at org.wildfly.security.auth.client.XmlConfigurationTest.testWrongRuleOrder(XmlConfigurationTest.java:93)
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-613) Some nested classes should be considered to be static nested in Elytron
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-613?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-613:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> Some nested classes should be considered to be static nested in Elytron
> -----------------------------------------------------------------------
>
> Key: ELY-613
> URL: https://issues.jboss.org/browse/ELY-613
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta7
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Labels: static_analysis
> Fix For: 1.1.0.Beta10
>
>
> There are some inner classes in Elytron which should be considered to be static nested to avoid dependency on their outer class. Following nested classes should be considered:
> * LoadedIdentity and Identity from org.wildfly.security.auth.realm.FileSystemSecurityRealm
> * DecoderState from org.wildfly.security.asn1.DERDecoder
> * AccountEntry from org.wildfly.security.auth.realm.LegacyPropertiesSecurityRealm
> * JaasAuthorizationIdentity and DefaultCallbackHandler from org.wildfly.security.auth.realm.JaasSecurityRealm
> * LoadKey from org.wildfly.security.keystore.AtomicLoadKeyStore
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-609) Unguarded read in ElytronPolicyConfiguration
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-609?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-609:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> Unguarded read in ElytronPolicyConfiguration
> --------------------------------------------
>
> Key: ELY-609
> URL: https://issues.jboss.org/browse/ELY-609
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta7
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Labels: static_analysis
> Fix For: 1.1.0.Beta10
>
>
> Access to fields {{uncheckedPermissions}}, {{excludedPermissions}} and {{rolePermissions}} in {{org.wildfly.security.authz.jacc.ElytronPolicyConfiguration}} is holded by lock. However lock is not used in their getter methods. Getters should be also handled by locks to avoid unguarded read of those fields.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-558) Introduce generalized support for authentication timeout of mechanisms
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-558?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-558:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> Introduce generalized support for authentication timeout of mechanisms
> ----------------------------------------------------------------------
>
> Key: ELY-558
> URL: https://issues.jboss.org/browse/ELY-558
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Mechanisms, Utils
> Reporter: David Lloyd
> Assignee: Farah Juma
> Fix For: 1.1.0.Beta10
>
>
> Paraphrasing from HipChat discussion.
> Generic mechanism wrappers for handling authentication timeout will not only support OTP-style credential read-modify-write authentication mechanisms, but generally avoid certain DoS conditions and failure states that would be associated with long locking of credentials (even in the read case).
> This issue is to implement a wrapping mechanism factory (for at least SASL and possibly HTTP as well, eventually) which supports authentication timeout by judicious usage of concurrency primitives and timed executors. It is important to guarantee thread-safe access to the underlying mechanism, which are generally concurrency-unsafe.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-524) Caching support in the LDAP realm
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-524?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-524:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> Caching support in the LDAP realm
> ---------------------------------
>
> Key: ELY-524
> URL: https://issues.jboss.org/browse/ELY-524
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Realms
> Reporter: David Lloyd
> Assignee: Pedro Igor
> Priority: Critical
> Fix For: 1.1.0.Beta10
>
>
> The LDAP realm should use a caching strategy to avoid excessive database load in the presence of per-request authentication traffic.
> The realm implementation could maintain a synchronized LRU cache of one-time-initialize references to a cached DirContext or Attributes or binding or some combination of these. Because the cache is synchronized, the one-time-initialize object would be added under the lock and then the lock released before the object is populated and returned as a cached credential, allowing atomic action with a minimum of contention.
> For each cached entity, a NamingListener could be established which would invalidate (or possibly update) the cached value as the database changes.
> Alternatively, a NamingListener could be established for all identities, and each update would invalidate or update any cached values corresponding to the DN or resolved name.
> This is a complex design topic so discussion is welcome.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-624) Add support for SSO and Clustered SSO
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-624?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-624:
---------------------------------
Fix Version/s: 1.1.0.Beta10
(was: 1.1.0.Beta9)
> Add support for SSO and Clustered SSO
> -------------------------------------
>
> Key: ELY-624
> URL: https://issues.jboss.org/browse/ELY-624
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Pedro Igor
> Priority: Critical
> Fix For: 1.1.0.Beta10
>
>
> This issue is to cover the APIs / SPIs and some implementation where Elytron is to be used with container managed SSO / Clustered SSO.
> By this we mean authentication mechanisms similar to HTTP Form where we want the resulting SecurityIdentity to be re-used across different HTTP context and possibly in the clustered case across different nodes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1800) Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1800?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-1800:
----------------------------------------
Assignee: (was: Brian Stansberry)
> Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1800
> URL: https://issues.jboss.org/browse/WFCORE-1800
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: James Perkins
> Attachments: WFCORE-1800.patch
>
>
> If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists.
> Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist.
> {code}
> /path=invalid(name=name)
> {code}
> For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH.
> The attached patch simply invokes the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} before the invocation of the custom OSH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1800) Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1800?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1800:
------------------------------------------
Background comment on this for anyone interested in it that I mentioned to James when we were discussing this:
[10:10 AM] Brian Stansberry: a kernel-wide fix just makes me nervous about unintentionally breaking something
[10:11 AM] James R Perkins: Okay. It made me a bit nervous too which is why I didn't submit a PR :)
[10:12 AM] Brian Stansberry: I think a long time ago we said that runtime-only resources still have to expose a Resource in the tree, but I believe that was still after a lot of subsystems were written
Basically a fix for this would likely further enforce the rule that a Resource must be present in the tree, which may break some old stuff. I think it's the right thing to do at some point anyway, but as part of it we need to recognize the potential for breakage and do some analysis of runtime-only resources to ensure they are done correctly.
TBH there may have been some other changes (e.g. in read-resource handling) that would have resulted in breakage if this rule wasn't being followed. But we should be cautious.
> Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1800
> URL: https://issues.jboss.org/browse/WFCORE-1800
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: James Perkins
> Assignee: Brian Stansberry
> Attachments: WFCORE-1800.patch
>
>
> If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists.
> Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist.
> {code}
> /path=invalid(name=name)
> {code}
> For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH.
> The attached patch simply invokes the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} before the invocation of the custom OSH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1291) Rule Compilation errors on mac and windows
by Robert (Bob) Brodt (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1291?page=com.atlassian.jira.plugi... ]
Robert (Bob) Brodt closed DROOLS-1291.
--------------------------------------
Release Notes Text: A change in the Eclipse Neon JDT surfaced a bug in the Drools Java compiler interface. This was not an issue with the Eclipse Mars JDT.
Fix Version/s: 6.5.0.CR2
Resolution: Duplicate Issue
This is a duplicate of DROOLS-1250
> Rule Compilation errors on mac and windows
> ------------------------------------------
>
> Key: DROOLS-1291
> URL: https://issues.jboss.org/browse/DROOLS-1291
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Environment: RHDS 10.0.0.GA + RHDSIS 10.0.0.Alpha1 (JBoss Drools 6.4.1.Final-v20160503-1355-B205)
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Priority: Blocker
> Fix For: 6.5.0.CR2
>
> Attachments: drools_error.png
>
>
> The following error occurs on mac and windows after creating a drools project in Problems view
> {code}
> Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1800) Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1800?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-1800:
----------------------------------
Description:
If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists.
Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist.
{code}
/path=invalid(name=name)
{code}
For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH.
The attached patch simply invokes the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} before the invocation of the custom OSH.
was:
If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists.
Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist.
{code}
/path=invalid(name=name)
{code}
For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH.
> Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1800
> URL: https://issues.jboss.org/browse/WFCORE-1800
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: James Perkins
> Assignee: Brian Stansberry
> Attachments: WFCORE-1800.patch
>
>
> If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists.
> Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist.
> {code}
> /path=invalid(name=name)
> {code}
> For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH.
> The attached patch simply invokes the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} before the invocation of the custom OSH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1800) Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1800?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-1800:
----------------------------------
Description:
If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists.
Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist.
{code}
/path=invalid(name=name)
{code}
For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH.
was:
If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists.
Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist.
{code}
/path=invalid(name=name)
{code}
> Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1800
> URL: https://issues.jboss.org/browse/WFCORE-1800
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: James Perkins
> Assignee: Brian Stansberry
> Attachments: WFCORE-1800.patch
>
>
> If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists.
> Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist.
> {code}
> /path=invalid(name=name)
> {code}
> For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1800) Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
by James Perkins (JIRA)
James Perkins created WFCORE-1800:
-------------------------------------
Summary: Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers
Key: WFCORE-1800
URL: https://issues.jboss.org/browse/WFCORE-1800
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: James Perkins
Assignee: Brian Stansberry
If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists.
Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist.
{code}
/path=invalid(name=name)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-623) Checking for anonymous principal by name is insufficient
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-623?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse reassigned ELY-623:
------------------------------------
Assignee: Jan Kalina (was: Darran Lofthouse)
> Checking for anonymous principal by name is insufficient
> --------------------------------------------------------
>
> Key: ELY-623
> URL: https://issues.jboss.org/browse/ELY-623
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: David Lloyd
> Assignee: Jan Kalina
>
> In {{src/main/java/org/wildfly/security/auth/server/SecurityIdentity.java}}:
> {noformat}
> + if (AnonymousPrincipal.getInstance().getName().equals(name)) {
> + if (! context.authorizeAnonymous(false)) {
> + throw log.runAsAuthorizationFailed(getPrincipal(), new AnonymousPrincipal(), null);
> + }
> + } else {
> + if (! (context.importIdentity(this) && context.authorize(name, authorize))) {
> + throw log.runAsAuthorizationFailed(getPrincipal(), new NamePrincipal(name), null);
> + }
> }
> {noformat}
> Only a type check is sufficient to determine if a principal is anonymous. In this fix, the string name "anonymous" takes on a special meaning for the first time, which should not be the case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7119) Introduce new web session granularity for consistent fine granularity replication
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-7119:
----------------------------------
Summary: Introduce new web session granularity for consistent fine granularity replication
Key: WFLY-7119
URL: https://issues.jboss.org/browse/WFLY-7119
Project: WildFly
Issue Type: Feature Request
Components: Clustering
Affects Versions: 10.1.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 11.0.0.Alpha1
Currently, ATTRIBUTE granularity sessions are vulnerable to partial stale reads, where some session attributes might have current data, and some are stale. For some use cases, this might be intolerable. For these use cases, we should introduce a new session granularity that tracks a version or checksum per attribute, that we can use to detect stale attribute cache entries.
This new granularity would retain the performance benefits of ATTRIBUTE granularity replication while maintaining the attribute consistency guarantees of SESSION granularity replication.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1291) Rule Compilation errors on mac and windows
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1291?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky commented on DROOLS-1291:
-------------------------------------------
Note that all java classes can be executed without any problem
> Rule Compilation errors on mac and windows
> ------------------------------------------
>
> Key: DROOLS-1291
> URL: https://issues.jboss.org/browse/DROOLS-1291
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Environment: RHDS 10.0.0.GA + RHDSIS 10.0.0.Alpha1 (JBoss Drools 6.4.1.Final-v20160503-1355-B205)
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Priority: Blocker
> Attachments: drools_error.png
>
>
> The following error occurs on mac and windows after creating a drools project in Problems view
> {code}
> Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1291) Rule Compilation errors on mac and windows
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1291?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated DROOLS-1291:
--------------------------------------
Steps to Reproduce:
# Open the wizard for Drools project
# Select the option in the middle (a project with examples)
# Select a runtime, e.g. BRMS 6.3.0.GA
# Press Finish and open Problems view
> Rule Compilation errors on mac and windows
> ------------------------------------------
>
> Key: DROOLS-1291
> URL: https://issues.jboss.org/browse/DROOLS-1291
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Environment: RHDS 10.0.0.GA + RHDSIS 10.0.0.Alpha1 (JBoss Drools 6.4.1.Final-v20160503-1355-B205)
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Priority: Blocker
> Attachments: drools_error.png
>
>
> The following error occurs on mac and windows after creating a drools project in Problems view
> {code}
> Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1291) Rule Compilation errors on mac and windows
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1291?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated DROOLS-1291:
--------------------------------------
Description:
The following error occurs on mac and windows after creating a drools project in Problems view
{code}
Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
KnowledgeHelper cannot be resolved to a type
com.sample.DroolsTest.Message cannot be resolved to a type
org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
java.lang.Exception cannot be resolved to a type
org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
Message.GOODBYE cannot be resolved to a type
org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
com.sample.DroolsTest.Message cannot be resolved to a type
{code}
was:
The following error occurs on mac and windows after creating a drools project in Problems view
> Rule Compilation errors on mac and windows
> ------------------------------------------
>
> Key: DROOLS-1291
> URL: https://issues.jboss.org/browse/DROOLS-1291
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Environment: RHDS 10.0.0.GA + RHDSIS 10.0.0.Alpha1 (JBoss Drools 6.4.1.Final-v20160503-1355-B205)
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Priority: Blocker
> Attachments: drools_error.png
>
>
> The following error occurs on mac and windows after creating a drools project in Problems view
> {code}
> Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1291) Rule Compilation errors on mac and windows
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created DROOLS-1291:
-----------------------------------------
Summary: Rule Compilation errors on mac and windows
Key: DROOLS-1291
URL: https://issues.jboss.org/browse/DROOLS-1291
Project: Drools
Issue Type: Bug
Components: eclipse plugin
Affects Versions: 6.4.0.Final
Environment: RHDS 10.0.0.GA + RHDSIS 10.0.0.Alpha1 (JBoss Drools 6.4.1.Final-v20160503-1355-B205)
Reporter: Andrej Podhradsky
Assignee: Robert (Bob) Brodt
Priority: Blocker
Attachments: drools_error.png
The following error occurs on mac and windows after creating a drools project in Problems view
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1290) NPE caused by forced flushing of unlinked path in stream mode
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-1290:
-----------------------------------
Summary: NPE caused by forced flushing of unlinked path in stream mode
Key: DROOLS-1290
URL: https://issues.jboss.org/browse/DROOLS-1290
Project: Drools
Issue Type: Bug
Components: core engine
Reporter: Mario Fusco
Assignee: Mario Fusco
Fix For: 7.0.0.Beta2
In stream mode it is necessary to enforce flushing of path memories. However doing this on an unlinked path is a waste of time and moreover can causes a NPE in presence of a subnetwork like the following:
{code}
java.lang.NullPointerException
at org.drools.core.phreak.RuleNetworkEvaluator.deleteChildLeftTuple(RuleNetworkEvaluator.java:725)
at org.drools.core.phreak.RuleNetworkEvaluator.unlinkAndDeleteChildLeftTuple(RuleNetworkEvaluator.java:718)
at org.drools.core.phreak.PhreakJoinNode.doLeftDeletes(PhreakJoinNode.java:418)
at org.drools.core.phreak.PhreakJoinNode.doNode(PhreakJoinNode.java:47)
at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:519)
at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:505)
at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341)
at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301)
at org.drools.core.phreak.RuleNetworkEvaluator.doRiaNode(RuleNetworkEvaluator.java:573)
at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:500)
at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341)
at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301)
at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136)
at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94)
at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194)
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73)
at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:969)
at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1311)
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1250)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1356)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1347)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1328)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1285) NPE caused by forced flushing of unlinked path in stream mode
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1285?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-1285.
---------------------------------
Fix Version/s: 7.0.0.Beta2
Resolution: Done
Fixed by https://github.com/droolsjbpm/drools/commit/e6da071fa
> NPE caused by forced flushing of unlinked path in stream mode
> -------------------------------------------------------------
>
> Key: DROOLS-1285
> URL: https://issues.jboss.org/browse/DROOLS-1285
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 7.0.0.Beta2
>
>
> In stream mode it is necessary to enforce flushing of path memories. However doing this on an unlinked path is a waste of time and moreover can causes a NPE in presence of a subnetwork like the following:
> {code}
> java.lang.NullPointerException
> at org.drools.core.phreak.RuleNetworkEvaluator.deleteChildLeftTuple(RuleNetworkEvaluator.java:725)
> at org.drools.core.phreak.RuleNetworkEvaluator.unlinkAndDeleteChildLeftTuple(RuleNetworkEvaluator.java:718)
> at org.drools.core.phreak.PhreakJoinNode.doLeftDeletes(PhreakJoinNode.java:418)
> at org.drools.core.phreak.PhreakJoinNode.doNode(PhreakJoinNode.java:47)
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:519)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:505)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301)
> at org.drools.core.phreak.RuleNetworkEvaluator.doRiaNode(RuleNetworkEvaluator.java:573)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:500)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:341)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:73)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:969)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1311)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1250)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1356)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1347)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1328)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JGRP-2030) GMS: view_ack_collection_timeout delay when last 2 members leave concurrently
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2030?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2030:
--------------------------------
[~dan.berindei]: can I close this?
> GMS: view_ack_collection_timeout delay when last 2 members leave concurrently
> -----------------------------------------------------------------------------
>
> Key: JGRP-2030
> URL: https://issues.jboss.org/browse/JGRP-2030
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.8
> Reporter: Dan Berindei
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.6.11, 4.0
>
>
> When the coordinator ({{NodeE}}) leaves, it tries to install a new view on behalf of the new coordinator ({{NodeG}}, the last member).
> {noformat}
> 21:33:26,844 TRACE (ViewHandler,InitialClusterSizeTest-NodeE-42422:) [GMS] InitialClusterSizeTest-NodeE-42422: mcasting view [InitialClusterSizeTest-NodeG-30521|3] (1) [InitialClusterSizeTest-NodeG-30521] (1 mbrs)
> 21:33:26,844 TRACE (ViewHandler,InitialClusterSizeTest-NodeE-42422:) [TCP_NIO2] InitialClusterSizeTest-NodeE-42422: sending msg to null, src=InitialClusterSizeTest-NodeE-42422, headers are GMS: GmsHeader[VIEW], NAKACK2: [MSG, seqno=1], TP: [cluster_name=ISPN]
> {noformat}
> The message is actually sent later by the bundler, but {{NodeG}} is also sending its {{LEAVE_REQ}} message at the same time. Both nodes try to create a connection to each other, and only {{NodeG}} succeeds:
> {noformat}
> 21:33:26,844 TRACE (ForkThread-2,InitialClusterSizeTest:) [TCP_NIO2] InitialClusterSizeTest-NodeG-30521: sending msg to InitialClusterSizeTest-NodeE-42422, src=InitialClusterSizeTest-NodeG-30521, headers are GMS: GmsHeader[LEAVE_REQ]: mbr=InitialClusterSizeTest-NodeG-30521, UNICAST3: DATA, seqno=1, conn_id=1, first, TP: [cluster_name=ISPN]
> 21:33:26,865 TRACE (Timer-2,InitialClusterSizeTest-NodeG-30521:) [TCP_NIO2] InitialClusterSizeTest-NodeG-30521: sending 1 msgs (83 bytes (0.27% of max_bundle_size) to 1 dests(s): [ISPN:InitialClusterSizeTest-NodeE-42422]
> 21:33:26,865 TRACE (Timer-2,InitialClusterSizeTest-NodeE-42422:) [TCP_NIO2] InitialClusterSizeTest-NodeE-42422: sending 1 msgs (91 bytes (0.29% of max_bundle_size) to 1 dests(s): [ISPN]
> 21:33:26,865 TRACE (Timer-2,InitialClusterSizeTest-NodeG-30521:) [TCP_NIO2] dest=127.0.0.1:7900 (86 bytes)
> 21:33:26,865 TRACE (Timer-2,InitialClusterSizeTest-NodeE-42422:) [TCP_NIO2] dest=127.0.0.1:7920 (94 bytes)
> 21:33:26,865 TRACE (Timer-2,InitialClusterSizeTest-NodeE-42422:) [TCP_NIO2] 127.0.0.1:7900: connecting to 127.0.0.1:7920
> 21:33:26,865 TRACE (Timer-2,InitialClusterSizeTest-NodeG-30521:) [TCP_NIO2] 127.0.0.1:7920: connecting to 127.0.0.1:7900
> 21:33:26,866 TRACE (NioConnection.Reader [null],InitialClusterSizeTest-NodeG-30521:) [TCP_NIO2] 127.0.0.1:7920: rejected connection from 127.0.0.1:7900 (connection existed and my address won as it's higher)
> 21:33:26,867 TRACE (OOB-1,InitialClusterSizeTest-NodeE-42422:) [TCP_NIO2] InitialClusterSizeTest-NodeE-42422: received [dst: InitialClusterSizeTest-NodeE-42422, src: InitialClusterSizeTest-NodeG-30521 (3 headers), size=0 bytes, flags=OOB], headers are GMS: GmsHeader[LEAVE_REQ]: mbr=InitialClusterSizeTest-NodeG-30521, UNICAST3: DATA, seqno=1, conn_id=1, first, TP: [cluster_name=ISPN]
> {noformat}
> I'm guessing {{NodeE}} would need a {{STABLE}} round in order to retransmit the {{VIEW}} message, but I'm not sure if the stable round would work, since it already (partially?) installed the new view with {{NodeG}} as the only member. However, I think it should be possible for {{NodeE}} to remove {{NodeG}} from it's {{AckCollector}} once it receives its {{LEAVE_REQ}}, and stop blocking.
> This is a minor annoyance a few the Infinispan tests - most of them shut down the nodes serially, so they don't see this delay.
> The question is whether the concurrent connection setup can have an impact for other messages as well - e.g. during startup, when there aren't a lot of messages being sent around to trigger retransmission. Could the node that failed to open its connection retry immediately on the connection opened by the other node?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1799) Property separator not appended after argument value if argument completer uses non-zero offset
by Bartosz Spyrko-Śmietanko (JIRA)
Bartosz Spyrko-Śmietanko created WFCORE-1799:
------------------------------------------------
Summary: Property separator not appended after argument value if argument completer uses non-zero offset
Key: WFCORE-1799
URL: https://issues.jboss.org/browse/WFCORE-1799
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0.Alpha7
Reporter: Bartosz Spyrko-Śmietanko
Assignee: Bartosz Spyrko-Śmietanko
Priority: Minor
For example:
module add --name=foo --dependencies=sun.scripting ==> space character is added at the end.
module add --name=foo --dependencies=sun.scripting,sun.jdk ==> Nothing happens, no space character added.
deployment-overlay add --name=foo --contents=foo=/some/file<TAB> ==> Nothing happens, no space character added.
This seems to be caused by a condition in [OperationRequestCompleter|https://github.com/wildfly/wildfly-core/blob/bc...] - if a suggested value is the same as current user input, ORC replaces the suggestion with a separator.
This only works if the offset returned by argument completer is 0 - if the completer provides only part of the value, this condition will never be triggered.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1785) Extension remove is not cleaning out provided capabilities
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1785?page=com.atlassian.jira.plugi... ]
Tomaz Cerar commented on WFCORE-1785:
-------------------------------------
Sent PR that properly implements removal of MRR so now we do recursive delete of all sub resources.
which also fixes this problem.
> Extension remove is not cleaning out provided capabilities
> ----------------------------------------------------------
>
> Key: WFCORE-1785
> URL: https://issues.jboss.org/browse/WFCORE-1785
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha7
> Reporter: Jan Tymel
> Assignee: Tomaz Cerar
> Labels: affects_elytron
> Fix For: 3.0.0.Alpha8
>
>
> It is not possible to add Elytron extension that was previously removed. Everything works fine if the server is reloaded between steps 5 and 6, hence I assume that there is either 'reload required' state missing or Elytron extension is not removed properly.
> Actual result:
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.security.providers' is already registered in context 'global'.",
> "rolled-back" => true
> }
> {code}
> {code}
> ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([("extension" => "org.wildfly.extension.elytron")]): java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.security.providers' is already registered in context 'global'.
> at org.jboss.as.controller.CapabilityRegistry.lambda$registerPossibleCapability$0(CapabilityRegistry.java:518)
> at java.util.concurrent.ConcurrentHashMap.computeIfPresent(ConcurrentHashMap.java:1769)
> at org.jboss.as.controller.CapabilityRegistry.registerPossibleCapability(CapabilityRegistry.java:512)
> at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerCapability(ConcreteResourceRegistration.java:669)
> at org.jboss.as.controller.SimpleResourceDefinition.registerCapabilities(SimpleResourceDefinition.java:368)
> at org.jboss.as.controller.registry.NodeSubregistry.registerChild(NodeSubregistry.java:108)
> at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:226)
> at org.wildfly.extension.elytron.ElytronDefinition.registerChildren(ElytronDefinition.java:83)
> at org.jboss.as.controller.registry.NodeSubregistry.registerChild(NodeSubregistry.java:107)
> at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:226)
> at org.jboss.as.controller.extension.ExtensionRegistry$SubsystemRegistrationImpl.registerSubsystemModel(ExtensionRegistry.java:694)
> at org.wildfly.extension.elytron.ElytronExtension.initialize(ElytronExtension.java:99)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:131)
> at org.jboss.as.controller.extension.ExtensionAddHandler.execute(ExtensionAddHandler.java:83)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:951)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:694)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:389)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
> Expected result:
> It is possible to add Elytron subsystem after its removal.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1793) add-content operation fails to overwrite existing content with overwrite=true set when passing content by file path
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1793?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet commented on WFCORE-1793:
-------------------------------------------
path is not a valid parameter, fixing the operation definition
> add-content operation fails to overwrite existing content with overwrite=true set when passing content by file path
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1793
> URL: https://issues.jboss.org/browse/WFCORE-1793
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha8
> Reporter: Michal Jurc
> Assignee: ehsavoie Hugonnet
>
> Upon overwriting content in managed exploded deployments on wildfly-core, the following errors are produced:
> {{CLI}}
> {code}[standalone@localhost:9990 /] deploy /home/mjurc/testing/eap7-204/jboss-kitchensink-ear.ear
> [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:undeploy
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:explode
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:deploy
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=true)
> {
> "outcome" => "failed",
> "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=false)
> {
> "outcome" => "failed",
> "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}])
> {
> "outcome" => "failed",
> "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment",
> "rolled-back" => true
> }{code}
> {{Server}}
> {code}09:41:36,029 WARN [org.jboss.as.repository] (management-handler-thread - 5) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content7797527203290314566/content/test.txt
> 09:45:27,505 WARN [org.jboss.as.repository] (management-handler-thread - 12) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content721393778736298367/content/test.txt
> 09:45:36,352 WARN [org.jboss.as.repository] (management-handler-thread - 10) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content344811471223714239/content/test.txt{code}
> This issue does not seem to arise when the content is passed to the server by input stream index.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-627) Elytron introduces SSL/TLS protocol constraints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-627?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina commented on ELY-627:
--------------------------------
Darran: "need a bit more of a discussion here on that one next week" => postponed
> Elytron introduces SSL/TLS protocol constraints
> -----------------------------------------------
>
> Key: ELY-627
> URL: https://issues.jboss.org/browse/ELY-627
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.1.0.Beta8
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
>
> {noformat}
> "protocols" => {
> "type" => LIST,
> "description" => "The enabled protocols.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "SSLv2",
> "SSLv3",
> "TLSv1",
> "TLSv1_1",
> "TLSv1_2",
> "TLSv1_3"
> ],
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {noformat}
> Why elytron on this place is going to validate user input and map standard java values [1] into proprietary values?
> Whereas on other similar places (KeyManager algorithm, TrustManager algorithm, Keystore types) it leaves up to user to set proper value.
> IMO, with such mapping another place, where bugs can raise was introduced. EAP will be here always one step back compared to java.
> Note, IBM java already today defines little bit different protocols set [2]
> I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardN...
> [2] http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7113) Naming subsystem does not expose a proper capability contract
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-7113?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-7113:
-----------------------------------
Issue Type: Bug (was: Feature Request)
Summary: Naming subsystem does not expose a proper capability contract (was: Expose capabilities for naming subsystem)
> Naming subsystem does not expose a proper capability contract
> -------------------------------------------------------------
>
> Key: WFLY-7113
> URL: https://issues.jboss.org/browse/WFLY-7113
> Project: WildFly
> Issue Type: Bug
> Components: Naming
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.Alpha1
>
>
> Subsystems that currently use JNDI bindings require that the naming subsystem be present. The naming subsystem should expose capabilities for which other subsystems can test for the presence, so they can function in the absence of the naming subsystem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7113) Expose capabilities for naming subsystem
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-7113?page=com.atlassian.jira.plugin.... ]
Paul Ferraro reassigned WFLY-7113:
----------------------------------
Assignee: Paul Ferraro
> Expose capabilities for naming subsystem
> ----------------------------------------
>
> Key: WFLY-7113
> URL: https://issues.jboss.org/browse/WFLY-7113
> Project: WildFly
> Issue Type: Feature Request
> Components: Naming
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.Alpha1
>
>
> Subsystems that currently use JNDI bindings require that the naming subsystem be present. The naming subsystem should expose capabilities for which other subsystems can test for the presence, so they can function in the absence of the naming subsystem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7113) Expose capabilities for naming subsystem
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7113?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-7113:
----------------------------------------
[~fjuma] FYI not assigned yet but I know you are looking at this subsystem as well.
> Expose capabilities for naming subsystem
> ----------------------------------------
>
> Key: WFLY-7113
> URL: https://issues.jboss.org/browse/WFLY-7113
> Project: WildFly
> Issue Type: Feature Request
> Components: Naming
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Fix For: 11.0.0.Alpha1
>
>
> Subsystems that currently use JNDI bindings require that the naming subsystem be present. The naming subsystem should expose capabilities for which other subsystems can test for the presence, so they can function in the absence of the naming subsystem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-338:
------------------------------------
Description: Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such. (was: Implement an option for a properly configured slave HC to promote itself to master after acquiring an exclusive lock mediated via some persistent store shared between all HCs that are possibly master.)
> Auto-promotion of slave HC to master
> ------------------------------------
>
> Key: WFCORE-338
> URL: https://issues.jboss.org/browse/WFCORE-338
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Ken Wills
>
> Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-338:
------------------------------------
Comment: was deleted
(was: This is lower priority now; I think using some sort of a quorum based voting protocol should be the primary approach for auto-promotion of a slave.
Anyone who wants this assigned to themselves, please discuss with me first.)
> Auto-promotion of slave HC to master
> ------------------------------------
>
> Key: WFCORE-338
> URL: https://issues.jboss.org/browse/WFCORE-338
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Ken Wills
>
> Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-338:
------------------------------------
Comment: was deleted
(was: Ken, see my comment above. This particular approach may not be something we want, but I'm assigning it to you as it's related to the general topic of an HA Domain Controller.)
> Auto-promotion of slave HC to master
> ------------------------------------
>
> Key: WFCORE-338
> URL: https://issues.jboss.org/browse/WFCORE-338
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Ken Wills
>
> Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-338:
------------------------------------
Summary: Auto-promotion of slave HC to master (was: Auto-promotion of slave HC to master based on a shared lock)
> Auto-promotion of slave HC to master
> ------------------------------------
>
> Key: WFCORE-338
> URL: https://issues.jboss.org/browse/WFCORE-338
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Ken Wills
>
> Implement an option for a properly configured slave HC to promote itself to master after acquiring an exclusive lock mediated via some persistent store shared between all HCs that are possibly master.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7113) Expose capabilities for naming subsystem
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-7113:
----------------------------------
Summary: Expose capabilities for naming subsystem
Key: WFLY-7113
URL: https://issues.jboss.org/browse/WFLY-7113
Project: WildFly
Issue Type: Feature Request
Components: Naming
Affects Versions: 10.1.0.Final
Reporter: Paul Ferraro
Fix For: 11.0.0.Alpha1
Subsystems that currently use JNDI bindings require that the naming subsystem be present. The naming subsystem should expose capabilities for which other subsystems can test for the presence, so they can function in the absence of the naming subsystem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-627) Elytron introduces SSL/TLS protocol constraints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-627?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina commented on ELY-627:
--------------------------------
*ProtocolSelector* and *CipherSuiteSelector* are very similar. Difference between current *ProtocolSelector* and *CipherSuiteSelector*:
* ProtocolSelector use hardcoded list of protocols
* CipherSuiteSelector obtain list of selectable ciphers from special object - MechanismDatabase
What exactly do you mean by "similar pattern"? Special object managing list of usable protocols?
> Elytron introduces SSL/TLS protocol constraints
> -----------------------------------------------
>
> Key: ELY-627
> URL: https://issues.jboss.org/browse/ELY-627
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.1.0.Beta8
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
>
> {noformat}
> "protocols" => {
> "type" => LIST,
> "description" => "The enabled protocols.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "SSLv2",
> "SSLv3",
> "TLSv1",
> "TLSv1_1",
> "TLSv1_2",
> "TLSv1_3"
> ],
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {noformat}
> Why elytron on this place is going to validate user input and map standard java values [1] into proprietary values?
> Whereas on other similar places (KeyManager algorithm, TrustManager algorithm, Keystore types) it leaves up to user to set proper value.
> IMO, with such mapping another place, where bugs can raise was introduced. EAP will be here always one step back compared to java.
> Note, IBM java already today defines little bit different protocols set [2]
> I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardN...
> [2] http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ELY-627) Elytron introduces SSL/TLS protocol constraints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-627?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina edited comment on ELY-627 at 9/15/16 7:50 AM:
---------------------------------------------------------
*ProtocolSelector* and *CipherSuiteSelector* are very similar. Difference between them:
* ProtocolSelector use hardcoded list of protocols
* CipherSuiteSelector obtain list of selectable ciphers from special object - MechanismDatabase
What exactly do you mean by "similar pattern"? Special object managing list of usable protocols?
was (Author: honza889):
*ProtocolSelector* and *CipherSuiteSelector* are very similar. Difference between current *ProtocolSelector* and *CipherSuiteSelector*:
* ProtocolSelector use hardcoded list of protocols
* CipherSuiteSelector obtain list of selectable ciphers from special object - MechanismDatabase
What exactly do you mean by "similar pattern"? Special object managing list of usable protocols?
> Elytron introduces SSL/TLS protocol constraints
> -----------------------------------------------
>
> Key: ELY-627
> URL: https://issues.jboss.org/browse/ELY-627
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.1.0.Beta8
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
>
> {noformat}
> "protocols" => {
> "type" => LIST,
> "description" => "The enabled protocols.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "SSLv2",
> "SSLv3",
> "TLSv1",
> "TLSv1_1",
> "TLSv1_2",
> "TLSv1_3"
> ],
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {noformat}
> Why elytron on this place is going to validate user input and map standard java values [1] into proprietary values?
> Whereas on other similar places (KeyManager algorithm, TrustManager algorithm, Keystore types) it leaves up to user to set proper value.
> IMO, with such mapping another place, where bugs can raise was introduced. EAP will be here always one step back compared to java.
> Note, IBM java already today defines little bit different protocols set [2]
> I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardN...
> [2] http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JGRP-2034) SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2034?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2034:
--------------------------------
What shall we do with this one?
[~NadirX]: unless you take some action on this, I'll close it, as I have neither knowledge of SASL nor running on some obscure JDK like IBM's... :-)
> SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
> ------------------------------------------------------------------------------------------
>
> Key: JGRP-2034
> URL: https://issues.jboss.org/browse/JGRP-2034
> Project: JGroups
> Issue Type: Bug
> Reporter: Ivan Straka
> Assignee: Tristan Tarrant
> Fix For: 3.6.11
>
>
> We see these two tests failing on IBM jdk 1.8
> org.jgroups.protocols.SASLTest-functional
> org.jgroups.protocols.SASL_SimpleAuthorizingCallbackTest-functional
> This issue may be related to https://issues.jboss.org/browse/JGRP-1993 somehow.
> There is standard output of tests.
> {code}
> ------------- testSASLDigestMD5 -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 521823 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 521823 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 521823 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 521825 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 521826 [DEBUG] GMS: B: sending JOIN(B) to A
> 521826 [TRACE] SASL: B: received CHALLENGE from A
> 521827 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 524826 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 524827 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 524827 [DEBUG] GMS: B: sending JOIN(B) to A
> 524828 [TRACE] SASL: B: received CHALLENGE from A
> 524828 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 526826 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@ad737f58
> ------------- testSASLDigestMD5Failure -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 529863 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 529864 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 529864 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 529866 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 529866 [DEBUG] GMS: B: sending JOIN(B) to A
> 529867 [TRACE] SASL: B: received CHALLENGE from A
> 529867 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 532867 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 532867 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 532867 [DEBUG] GMS: B: sending JOIN(B) to A
> 532868 [TRACE] SASL: B: received CHALLENGE from A
> 532869 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 534867 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@6f6c2511
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JGRP-2092) MERGE3: merge never happens
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2092?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2092:
--------------------------------
[~ndillman]: if you can reproduce the issue in your test system (perhaps without your staggering code), and then try 3.6, and can confirm that this fixes the issue, that would be great!
> MERGE3: merge never happens
> ---------------------------
>
> Key: JGRP-2092
> URL: https://issues.jboss.org/browse/JGRP-2092
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.6.11, 4.0
>
> Attachments: jgroups.txt
>
>
> (Reported by Neal Dillman)
> In the case below, a merge doesn't seem to happen. Write a unit test to reprodue this.
> {noformat}
> Host A view: B, X, Y, Z, A (where B should be coordinator)
> Host B view: C, Q, R, S, B (where C should be coordinator)
> Host C view: A, M, N, O, C (where A should be coordinator)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months