[JBoss JIRA] (WFLY-1033) Enhance XTS AS7 configuration
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-1033?page=com.atlassian.jira.plugin.... ]
David Lloyd reopened WFLY-1033:
-------------------------------
Assignee: (was: Gytis Trikleris)
If there is no intention to work this issue, it should be left open but unassigned, in case a community member wants to pick it up - unless it is determined that this should never be done for some reason.
> Enhance XTS AS7 configuration
> -----------------------------
>
> Key: WFLY-1033
> URL: https://issues.jboss.org/browse/WFLY-1033
> Project: WildFly
> Issue Type: Enhancement
> Components: XTS
> Reporter: Andrew Dinn
> Priority: Minor
> Fix For: 11.0.0.Alpha1
>
>
> The current integration of XTS into AS7 as an AS7 extension allows optional configuration of the coordinator URL from the <xts/> element in the AS7 standalone configuration file. No other configuration options are currently supported.
> XTS ought to support more precise configuration. IN particular, it ought to be possible to enable or disable deployment of coordinator, participant or client services independently and also to choose whether to deploy WS-AT or WS-BA services or both. This requires selectively deploying only the required web service endpoints, selectively executing the required initialization routines and selectively loading the required high level service implementations and context factory implementations.
> The XTS implementation has already been factored so as to to support such discriminated bootstrapping. So this task only requires modifying the AS7 extension code to manage the relevant configuration information and install the relevant values into the XTS environment configuration beans before starting the XTS service.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-6966) FatalError on Transaction Expired Entry Monitor during server shutdown
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-6966?page=com.atlassian.jira.plugin.... ]
David Lloyd reopened WFLY-6966:
-------------------------------
AFAIK it has always been a policy that there are no errors on shutdown, since day one. In any event, community issues should not be closed unless they are either done, or it is determined that they _should not_ be done. Otherwise leave them open for community contributors (maybe unassign them if you don't intend to work this issue).
> FatalError on Transaction Expired Entry Monitor during server shutdown
> ----------------------------------------------------------------------
>
> Key: WFLY-6966
> URL: https://issues.jboss.org/browse/WFLY-6966
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP, Transactions
> Affects Versions: 10.1.0.CR1
> Reporter: Ondra Chaloupka
> Assignee: Tomasz Adamski
> Priority: Minor
>
> I do experience intermittent errors being shown in server log during server shutdown. It happens time to time for server configured to use {{JTS}} transaction that {{Transaction Expired Entry Monitor}} shows {{FatalError}} during container shutdown.
> I do experience this failure when jdbc object store is used.
> The shutdown log looks
> {code}
> 2016-08-16 07:07:46,900 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment wmq.jmsra.rar (runtime-name: wmq.jmsra.rar) in 132ms
> 2016-08-16 07:07:46,914 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
> 2016-08-16 07:07:46,914 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> 2016-08-16 07:07:46,915 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
> 2016-08-16 07:07:46,921 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2
> 2016-08-16 07:07:46,924 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment crashrecovery-jms-stateless-cmt.jar (runtime-name: crashrecovery-jms-stateless-cmt.jar) in 156ms
> 2016-08-16 07:07:46,947 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 16) WFLYCLINF0003: Stopped client-mappings cache from ejb container
> 2016-08-16 07:07:46,952 TRACE [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) InputObjectState::InputObjectState(0:ffff7f000001:55f44a88:57b2ec0b:8, Recovery/FactoryContact)
> 2016-08-16 07:07:46,959 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 32) AMQ151003: resource adaptor stopped
> 2016-08-16 07:07:46,962 TRACE [com.arjuna.orbportability] (MSC service thread 1-4) ORB::shutdown ()
> 2016-08-16 07:07:46,962 TRACE [com.arjuna.orbportability] (MSC service thread 1-4) OA::destroyRootPOA ()
> 2016-08-16 07:07:46,962 TRACE [com.arjuna.orbportability] (MSC service thread 1-4) RootOA::shutdownObject (Servant)
> 2016-08-16 07:07:46,962 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-4) ARJUNA032018: Destroying TransactionManagerService
> 2016-08-16 07:07:46,963 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-4) ARJUNA032014: Stopping transaction recovery manager
> 2016-08-16 07:07:47,000 FATAL [com.arjuna.ats.jts] (Transaction Expired Entry Monitor) ARJUNA022006: The ORB has not been initialized yet
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) Exception in thread "Transaction Expired Entry Monitor" com.arjuna.ats.arjuna.exceptions.FatalError
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.ORBManager.getORB(ORBManager.java:56)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItem.restore_state(FactoryContactItem.java:264)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItem.restoreMe(FactoryContactItem.java:320)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.FactoryContactItem.recreate(FactoryContactItem.java:100)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.jts.recovery.contact.ExpiredContactScanner.scan(ExpiredContactScanner.java:99)
> 2016-08-16 07:07:47,001 ERROR [stderr] (Transaction Expired Entry Monitor) at com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:171)
> 2016-08-16 07:07:47,001 DEBUG [com.arjuna.ats.arjuna] (Listener:4712) Recovery listener existing com.arjuna.ats.internal.arjuna.recovery.WorkerService
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-4) PeriodicRecovery: Mode <== TERMINATED
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-4) PeriodicRecovery: shutdown waiting for scan to end
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: scan TERMINATED at phase 1
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread Status <== INACTIVE
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread exiting
> 2016-08-16 07:07:47,002 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-4) PeriodicRecovery: shutdown scan wait complete
> 2016-08-16 07:07:47,003 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0010: Unbound data source [java:jboss/datasources/jdbc-store]
> 2016-08-16 07:07:47,006 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Stopped Driver service with driver-name = module_postgresql-9.4.1207.jar
> 2016-08-16 07:07:47,012 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 32) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.SP16-redhat-1 [023d1e88-638c-11e6-927a-a180c25082cf] stopped
> 2016-08-16 07:07:47,012 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTP listener default suspending
> 2016-08-16 07:07:47,013 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
> 2016-08-16 07:07:47,013 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0004: Undertow 1.3.21.Final-redhat-1 stopping
> 2016-08-16 07:07:47,018 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) stopped in 250ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFCORE-1902) Error messages from CLI batch should be more informative
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1902?page=com.atlassian.jira.plugi... ]
Marek Kopecký commented on WFCORE-1902:
---------------------------------------
[~jdenise]: WDYT about this feature request in current CLI? What about CLI next and this feature?
> Error messages from CLI batch should be more informative
> --------------------------------------------------------
>
> Key: WFCORE-1902
> URL: https://issues.jboss.org/browse/WFCORE-1902
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Affects Versions: 3.0.0.Alpha10
> Reporter: Marek Kopecký
> Assignee: Jean-Francois Denise
>
> *Description of problem:*
> Error messages from CLI batch should be more informative
> *Steps to Reproduce:*
> {noformat}
> cat <<EOF >a
> batch
> :read-attribute(name=product-version)
> :read-attribute(name=product-name)
> :read-attribute(name=nonsence)
> :read-attribute(name=product-name)
> run-batch
> EOF
> ./jboss-cli.sh -c --file=a
> {noformat}
> *Actual results:*
> {noformat}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0201: Unknown attribute 'nonsence'"}}
> {noformat}
> *Expected results:*
> I can imagine content like following could be helpful for troubleshooting:
> {noformat}
> {
> "WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
> "Operation step-3" => {
> "line number" => 4
> "operation" => ":read-attribute(name=nonsence)"
> "response" => "WFLYCTL0201: Unknown attribute 'nonsence'"
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFCORE-1902) Error messages from CLI batch should be more informative
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1902?page=com.atlassian.jira.plugi... ]
Marek Kopecký reassigned WFCORE-1902:
-------------------------------------
Assignee: Jean-Francois Denise
> Error messages from CLI batch should be more informative
> --------------------------------------------------------
>
> Key: WFCORE-1902
> URL: https://issues.jboss.org/browse/WFCORE-1902
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Affects Versions: 3.0.0.Alpha10
> Reporter: Marek Kopecký
> Assignee: Jean-Francois Denise
>
> *Description of problem:*
> Error messages from CLI batch should be more informative
> *Steps to Reproduce:*
> {noformat}
> cat <<EOF >a
> batch
> :read-attribute(name=product-version)
> :read-attribute(name=product-name)
> :read-attribute(name=nonsence)
> :read-attribute(name=product-name)
> run-batch
> EOF
> ./jboss-cli.sh -c --file=a
> {noformat}
> *Actual results:*
> {noformat}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0201: Unknown attribute 'nonsence'"}}
> {noformat}
> *Expected results:*
> I can imagine content like following could be helpful for troubleshooting:
> {noformat}
> {
> "WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
> "Operation step-3" => {
> "line number" => 4
> "operation" => ":read-attribute(name=nonsence)"
> "response" => "WFLYCTL0201: Unknown attribute 'nonsence'"
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFCORE-1902) Error messages from CLI batch should be more informative
by Marek Kopecký (JIRA)
Marek Kopecký created WFCORE-1902:
-------------------------------------
Summary: Error messages from CLI batch should be more informative
Key: WFCORE-1902
URL: https://issues.jboss.org/browse/WFCORE-1902
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Affects Versions: 3.0.0.Alpha10
Reporter: Marek Kopecký
*Description of problem:*
Error messages from CLI batch should be more informative
*Steps to Reproduce:*
{noformat}
cat <<EOF >a
batch
:read-attribute(name=product-version)
:read-attribute(name=product-name)
:read-attribute(name=nonsence)
:read-attribute(name=product-name)
run-batch
EOF
./jboss-cli.sh -c --file=a
{noformat}
*Actual results:*
{noformat}
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0201: Unknown attribute 'nonsence'"}}
{noformat}
*Expected results:*
I can imagine content like following could be helpful for troubleshooting:
{noformat}
{
"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
"Operation step-3" => {
"line number" => 4
"operation" => ":read-attribute(name=nonsence)"
"response" => "WFLYCTL0201: Unknown attribute 'nonsence'"
}
}
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (ELY-691) Elytron properties-realm is not compatible with legacy user property files
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-691?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina reassigned ELY-691:
------------------------------
Assignee: Jan Kalina (was: Darran Lofthouse)
> Elytron properties-realm is not compatible with legacy user property files
> --------------------------------------------------------------------------
>
> Key: ELY-691
> URL: https://issues.jboss.org/browse/ELY-691
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta11
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Blocker
>
> When users properties file (e.g. mgmt-users.properties) used by legacy properties security realm is taken and used with Elytron properties-realm (backed by {{org.wildfly.security.auth.realm.LegacyPropertiesSecurityRealm}}) then there exist username/password combinations which do not works correctly.
> Following scenarios which uses mentioned below username/password work correctly for properties file used by legacy solution and do not work for Elytron:
> {code}
> elytron:password // results to username elytron with password password
> elytronumlautöäü=password // results to username elytronumlautöäü with password password
> elytron用戶=password // results to username elytron用戶 with password password
> backslash\\=password // results to username backslash\ with password password
> backslash\\inthemiddle=password // results to username backslash\inthemiddle with password password
> dn\=elytron,dc\=wildfly,dc\=org=password // results to username dn=elytron,dc=wildfly,dc=org with password password
> elytron1=pass=word // results to username elytron1 with password pass=word - covered by JBEAP-6581
> elytron2=password\\ // results to username elytron2 with password password\
> elytron3=pass\\word // results to username elytron3 with password pass\word
> elytron4=passwordWithumlautöäü // results to username elytron4 with password passwordWithumlautöäü
> elytron5=用戶 // results to username elytron5 with password 用戶
> {code}
> Also '!' can be used for comments. It means that {{!elytron=password}} should not be considered as user {{!elytron}} but as comment.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (DROOLS-1345) Drop support for JSR94 integration?
by Petr Široký (JIRA)
Petr Široký created DROOLS-1345:
-----------------------------------
Summary: Drop support for JSR94 integration?
Key: DROOLS-1345
URL: https://issues.jboss.org/browse/DROOLS-1345
Project: Drools
Issue Type: Task
Components: core engine
Affects Versions: 7.0.0.Beta2
Reporter: Petr Široký
Assignee: Petr Široký
Drools JSR94 integration seems to be unused and unmaintained. Could we remote it for 7.x?
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (SASL-78) Invalid manifest section in jboss-sasl JAR
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/SASL-78?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse commented on SASL-78:
--------------------------------------
This project has now been superseded by the WildFly Elytron project - in what context is this being used? Are you using it when communicating with JBoss / WildFly?
> Invalid manifest section in jboss-sasl JAR
> ------------------------------------------
>
> Key: SASL-78
> URL: https://issues.jboss.org/browse/SASL-78
> Project: SASL Provider
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.0.4.Final, 1.0.5.Final
> Reporter: Björn Kautler
> Assignee: Darran Lofthouse
>
> In the {{MANIFEST.MF}} of your {{jboss-sasl}} JAR you have a section {{Build-Information}}.
> This violates that JAR specification.
> A section in the manifest always refers to an entry in the JAR.
> If you have sections in the manifest that do not refer to an entry in the JAR, it is assumed that the JAR was tampered with as there are entries missing that are referenced in the manifest.
> Please either remove this section and include the entries in that secion in the main section which is according to the specification or include a file called {{Build-Information}} at the root of your JAR file. (You are still using jboss-parent 7, if you upgrade to 8 or newer, the problem will be gone)
> ----
> In my concrete use-case this happened with other JARs with invalid manifest entries:
> - I have signed those JARs and included them in a WebStart application
> - I started the application with 8u102 32-bit {{javaws}}
> - The JARs were downloaded and their entries signatures verified
> - As there were entries in the manifest that are not present in the JAR, the file was not seen as completely signed with one signature, but Java remembered for each entry with which signature it was signed
> This already is not too nice as it slows down the application as now for each class that gets loaded the signature has to be retrieved from a map and a list instead of having just one signature for all entries. But it gets much worse:
> - The acutal application was to be executed with 8u102 64-bit, so the 32-bit one wrote its session information out into files, including the information about verified JARs and also their entries if needed, and starts the 64-bit JVM
> - The 64-bit JVM loads this session information and thus does not have to do the time-consuming verification of the JARs all over again
> - Unfortunately since 8u91 or so there is a bug in this session reading and writing algorithm, so that some of the entry names get crippled with additional characters in-between
> - If now a class should be loaded that has such a crippled entry in the JAR-entry-to-signature map, the entry is not found and the class is considered as not signed which will block the application from further execution
> Of course this second part is a bug in Java, but it would work flawlessly if the JARs would not have invalid sections.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months