May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6661) Bean level lock type not applied

by Keio Kraaner (JIRA)

Keio Kraaner created WFLY-6661: ---------------------------------- Summary: Bean level lock type not applied Key: WFLY-6661 URL: https://issues.jboss.org/browse/WFLY-6661 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 10.0.0.Final Reporter: Keio Kraaner A singleton EJB has @Lock(LockType.READ) annotation declared on the class level. The bean is accessed using a local (defined by @Local annotation) or remote (defined by @Remote annotation) EJB interface. SingletonComponent::getLockType returns wrong value (LockType.WRITE) because the beanLevelLockType map does not contain a key equal to the local or remote interface class name. It contains a key equal to the EJB class name that implements those interfaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Description: It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 to JBoss EAP 7 or creating non-XA datasource for using local transactions in JBoss EAP 7. In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7. was: It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource for using local transactions in JBoss EAP 7. In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7. > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Environment: JBoss EAP 7.0.0 > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 to JBoss EAP 7 or creating non-XA datasource for using local transactions in JBoss EAP 7. > In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6660) Allow to dump Artemis journal to file by CLI operation

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-6660?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-6660: -------------------------------------- Yes, I saw this warning as well. Question is if this is because that all journal operations must be suspended for a while or it can corrupt the journal. > Allow to dump Artemis journal to file by CLI operation > ------------------------------------------------------ > > Key: WFLY-6660 > URL: https://issues.jboss.org/browse/WFLY-6660 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Attachments: journal.txt > > > For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. > New CLI operation like {{print-journal-date-content}} would print content of journal to a file. > It would do the same thing like following Artemis CLI command: > {code} > .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages > {code} > This should work only in Admin only mode as dumping journal in run-time is not possible when data changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Environment: JBoss EAP 7.0.0 > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Environment: JBoss EAP 7.0.0 > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource for using local transactions in JBoss EAP 7. > In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-433) git backend for loading/storing the configuration XML for wildfly

by James Strachan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-433?page=com.atlassian.jira.plugin... ] James Strachan commented on WFCORE-433: --------------------------------------- BTW we have an implementation of a reusable microservice or command for automatically upgrading the git commit sha used to provide configuration files from git in kubernetes here: https://github.com/fabric8io/gitcontroller This lets you mount configuration files to a volume in kubernetes; such as this example: https://github.com/jstrachan/springboot-config-demo/blob/master/src/main/... so provided the standalone.xml files or whatever are stored in git; it'd be easy to use them in an EAP/wildfly/wildfly swarm docker image. The only thing to watch with gitRepo volumes with kubernetes is to ensure that the configuration files are mounted to a folder that your microservice can then read them from (and you don't try and mix and match the same folder for configuration and secrets/code). There's more detail on the configuration tradeoffs of microservices on kubernetes here: http://fabric8.io/guide/develop/configuration.html > git backend for loading/storing the configuration XML for wildfly > ----------------------------------------------------------------- > > Key: WFCORE-433 > URL: https://issues.jboss.org/browse/WFCORE-433 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: James Strachan > Assignee: Jason Greene > > when working with wildfly in a cloud/paas environment (like openshift, fabric8, docker, heroku et al) it'd be great to have a git repository for the configuration folder so that writes work something like: > * git pull > * write the, say, standalone.xml file > * git commit -a -m "some comment" > * git push > (with a handler to deal with conflicts; such as last write wins). > Then an optional periodic 'git pull' and reload configuration if there is a change. > This would then mean that folks could use a number of wildfly containers using docker / openshift / fabric8 and then have a shared git repository (e.g. the git repo in openshift or fabric8) to configure a group of wildfly containers. Folks could then reuse the wildfly management console within cloud environments (as the management console would, under the covers, be loading/saving from/to git) > Folks could then benefit from git tooling when dealing with versioning and audit logs of changes to the XML; along with getting the benefit of branching, tagging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6660) Allow to dump Artemis journal to file by CLI operation

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6660?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-6660: ----------------------------------- I'm not sure about that: the Artemis command has this warning: "Print data records information (WARNING: don't use while a production server is running)" [~ataylor] would it be "safe" to execute this command on a running Artemis server or should it be allowed only on admin-only server (ie no Artemis runtime)? > Allow to dump Artemis journal to file by CLI operation > ------------------------------------------------------ > > Key: WFLY-6660 > URL: https://issues.jboss.org/browse/WFLY-6660 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Attachments: journal.txt > > > For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. > New CLI operation like {{print-journal-date-content}} would print content of journal to a file. > It would do the same thing like following Artemis CLI command: > {code} > .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages > {code} > This should work only in Admin only mode as dumping journal in run-time is not possible when data changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Description: It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource for using local transactions in JBoss EAP 7. In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7. was: It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource for using local transactions in JBoss EAP 7. > In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6660) Allow to dump Artemis journal to file by CLI operation

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-6660?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-6660: -------------------------------------- Dump to CLI appears to be ok. It's possible to redirect CLI output file like: {code}[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=DLQ:count-messages > number_of_messages.txt{code} Also I just figured out that it's possible to dump journal during runtime as well. So admin only mode is not required. > Allow to dump Artemis journal to file by CLI operation > ------------------------------------------------------ > > Key: WFLY-6660 > URL: https://issues.jboss.org/browse/WFLY-6660 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Attachments: journal.txt > > > For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. > New CLI operation like {{print-journal-date-content}} would print content of journal to a file. > It would do the same thing like following Artemis CLI command: > {code} > .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages > {code} > This should work only in Admin only mode as dumping journal in run-time is not possible when data changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6660) Allow to dump Artemis journal to file by CLI operation

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6660?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-6660: ----------------------------------- Artemis API provides only dump to the standard output. This operation would only dump to the CLI and can not store its output in a file. [~mnovak] Would you prefer to have the dump stored in a file (this requies a fix in Artemis) or is it acceptable to print the dump? > Allow to dump Artemis journal to file by CLI operation > ------------------------------------------------------ > > Key: WFLY-6660 > URL: https://issues.jboss.org/browse/WFLY-6660 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Attachments: journal.txt > > > For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. > New CLI operation like {{print-journal-date-content}} would print content of journal to a file. > It would do the same thing like following Artemis CLI command: > {code} > .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages > {code} > This should work only in Admin only mode as dumping journal in run-time is not possible when data changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6660) Allow to dump Artemis journal to file by CLI operation

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-6660?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFLY-6660: --------------------------------- Attachment: journal.txt This dump contains useful information for debugging of issues. It's possible to track which messages were processed in which transaction. Which jms transactions are unfinished and useful info about XA transactions. I'm attaching dump Artemis journal after one of our tests for review. > Allow to dump Artemis journal to file by CLI operation > ------------------------------------------------------ > > Key: WFLY-6660 > URL: https://issues.jboss.org/browse/WFLY-6660 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Attachments: journal.txt > > > For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. > New CLI operation like {{print-journal-date-content}} would print content of journal to a file. > It would do the same thing like following Artemis CLI command: > {code} > .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages > {code} > This should work only in Admin only mode as dumping journal in run-time is not possible when data changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016