[JBoss JIRA] (WFCORE-1731) Exception generated from command "connection-info" with embedded server
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1731?page=com.atlassian.jira.plugi... ]
Ingo Weiss reassigned WFCORE-1731:
----------------------------------
Assignee: Ingo Weiss (was: Alexey Loubyansky)
> Exception generated from command "connection-info" with embedded server
> -----------------------------------------------------------------------
>
> Key: WFCORE-1731
> URL: https://issues.jboss.org/browse/WFCORE-1731
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management, Security
> Affects Versions: 3.0.0.Alpha5
> Environment: JBoss Admin Command-line Interface
> JBOSS_HOME: C:\dev\jboss-eap-7.0.1
> JBoss AS release: 2.1.6.Final-redhat-1 "Kenny"
> JBoss AS product: JBoss EAP 7.0.1.GA
> JAVA_HOME: c:\java\jdk1.8.0_45
> java.version: 1.8.0_45
> java.vm.vendor: Oracle Corporation
> java.vm.version: 25.45-b02
> os.name: Windows 7
> os.version: 6.1
> Reporter: Petr Kremensky
> Assignee: Ingo Weiss
> Priority: Minor
>
> I started the embedded server and tried to obtain the connection information. An exception occurred:
> {code}
> [standalone@embedded /] connection-info
> 13:14:59,095 ERROR [org.jboss.as.controller.management-operation] (AeshProcess: 32) WFLYCTL0013: Operation ("whoami") failed - address: ([]): java.lang.IllegalArgumentException: newValue is null
> at org.jboss.dmr.ModelNode.set(ModelNode.java:499)
> at org.jboss.as.domain.management.security.WhoAmIOperation.execute(WhoAmIOperation.java:95)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204)
> at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:659)
> at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:649)
> at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerClient.java:63)
> at org.jboss.as.cli.embedded.ThreadContextsModelControllerClient.execute(ThreadContextsModelControllerClient.java:59)
> at org.jboss.as.cli.handlers.ConnectionInfoHandler.doHandle(ConnectionInfoHandler.java:74)
> at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:88)
> at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:776)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:799)
> at org.jboss.as.cli.impl.CommandContextImpl$2.execute(CommandContextImpl.java:412)
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:53)
> 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)
> WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: newValue is null
> Failed to handle 'connection-info': java.lang.NullPointerException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (HIBERNATE-156) Latency in EntityManager.createQuery(jpaQuery)
by Nidhal Ferchichi (JIRA)
Nidhal Ferchichi created HIBERNATE-156:
------------------------------------------
Summary: Latency in EntityManager.createQuery(jpaQuery)
Key: HIBERNATE-156
URL: https://issues.jboss.org/browse/HIBERNATE-156
Project: Hibernate Integration
Issue Type: Bug
Environment: hibernate 4.2.0.FINAL
Reporter: Nidhal Ferchichi
Assignee: Steve Ebersole
Priority: Critical
We have a latency issue on the process of query creation :
given this method :
public Collection executeJPQL(String jpaQuery, String persistenceUnit)
throws ServiceException {
EntityManager em = EntityManagerGetter.getEntityManager(
persistenceUnit, true);
//Some code here
Query query = em.createQuery(jpaQuery);
//Some code here
Collection result = query.getResultList();
//Some code here
return result;
}
The query is a JPQL query :
SELECT s.isin, sf.thirdPartySubFund$refBCT, s.currency$isoCode, acr.currency$isoCode, acr.navDecimalsNumber, s.shareType, s.shareStatus, s.investorType, c.investorType, st.subscriberTypeCode, cst.subscriberTypeCode, s.maximumSubscriptors, c.maximumSubscriptors, sf.isLotAccounting, s.marketingPeriodStartDate, c.marketingPeriodStartDate, sf.marketingPeriodStartDate, s.marketingPeriodEndDate, c.marketingPeriodEndDate, sf.marketingPeriodEndDate, tr.transactionRuleType, tr.amount, tr.shareQuantity, tr.minInvestCurrency$isoCode, tr.percentage, ctr.transactionRuleType, ctr.amount, ctr.shareQuantity, ctr.minInvestCurrency$isoCode, ctr.percentage, sftr.transactionRuleType, sftr.amount, sftr.shareQuantity, sftr.minInvestCurrency$isoCode, sftr.percentage, s.commissionBaseAmountType, c.commissionBaseAmountType, sf.commissionBaseAmountType, s.prepayment, c.prepayment, c.cashAccountingInAdvance, sf.cashAccountingInAdvance, s.isLockUp, c.isLockUp, sf.isLockUp, s.minNbrDaysLockUpPeriod, c.minNbrDaysLockUpPeriod, sf.minNbrDaysLockUpPeriod, dc.country$isoCode, s.bearerIF, s.clearerIF, s.nominativeIF, s.registeredIF, sf.europeanStandards, sf.euroRegulation, s.isCDSC, c.isCDSC, sf.isCDSC, s.cdscCommissionNAV, c.cdscCommissionNAV, sf.cdscCommissionNAV, tb.transactionType, ctb.transactionType, sftb.transactionType, s.quantityRoundingRule, sf.quantityRoundingType, s.startDate, s.endDate, tr.ruleStartDate, tr.ruleEndDate, ctr.ruleStartDate, ctr.ruleEndDate, sftr.ruleStartDate, sftr.ruleEndDate, tb.blockingStartDate, tb.blockingEndDate, ctb.blockingStartDate, ctb.blockingEndDate, sftb.blockingStartDate, sftb.blockingEndDate, sf.prepayment, s.initialNAVDate, s.initialSubscSens, s.initialSubscNbrDaysShift, s.initialSubscCutOff, s.initialSubscTimeZone, c.initialSubscSens, c.initialSubscNbrDaysShift, c.initialSubscCutOff, c.initialSubscTimeZone, sf.initialSubscSens, sf.initialSubscNbrDaysShift, sf.initialSubscCutOff, sf.initialSubscTimeZone, s.swingPrice, sf.swingPrice FROM com.caceis.cfr.fund.Share s JOIN s.subFund sf LEFT OUTER JOIN s.shareClass c LEFT OUTER JOIN s.subscriberType st LEFT OUTER JOIN c.subscriberType cst LEFT OUTER JOIN s.allowedCurrencies acr LEFT OUTER JOIN s.distributionCountry dc LEFT OUTER JOIN s.transactionRule tr LEFT OUTER JOIN c.transactionRule ctr LEFT OUTER JOIN sf.transactionRule sftr LEFT OUTER JOIN s.transactionBlocking tb LEFT OUTER JOIN c.transactionBlocking ctb LEFT OUTER JOIN sf.transactionBlocking sftb WHERE s.startDate <= TO_DATE('19-08-2016','dd-MM-yyyy') AND s.endDate >= TO_DATE('19-08-2016','dd-MM-yyyy') AND s.isin IN( 'FR0010373092','FR0010381905','FR0010371773') )
The creation of the query take about ~ 23 seconde . (em.createQuery()) .
The execution time take about 9 ms !!
The latency is in the creation of the query .
Is the 23 sec is an acceptable time ? How could we avoid this latency .
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (WFLY-6779) Add WISE for Web console access
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6779?page=com.atlassian.jira.plugin.... ]
Kabir Khan edited comment on WFLY-6779 at 8/30/16 10:59 AM:
------------------------------------------------------------
The pull request was merged and then reverted. After speaking to [~jason.greene] and [~brian.stansberry] it turned out that adding this deployment to our standard configs adds 2 seconds to boot time.
Please start a wildlfy-dev discussion.
was (Author: kabirkhan):
The pull request was merged and then reverted. After speaking to [~jason.greene] and [~brian.stansberry] it turned out that adding this deployment to our standard configs adds 2 seconds to boot time.
> Add WISE for Web console access
> -------------------------------
>
> Key: WFLY-6779
> URL: https://issues.jboss.org/browse/WFLY-6779
> Project: WildFly
> Issue Type: Feature Request
> Components: Web Console
> Reporter: R Searls
> Assignee: R Searls
> Priority: Minor
> Fix For: 11.0.0.Alpha1
>
>
> Wise is a Java framework for easily invoking webservices, which can be used as base for zero-code webservice invocation applications. (see http://wise.jboss.org/)
> Based upon Brian Stansberry's advise WISE is added to wfly using the "Mixed-Approach"
> for adding a feature.
> Once this is available in wfly. HAL can provide a link to it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (WFLY-6779) Add WISE for Web console access
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6779?page=com.atlassian.jira.plugin.... ]
Kabir Khan edited comment on WFLY-6779 at 8/30/16 10:46 AM:
------------------------------------------------------------
The pull request was merged and then reverted. After speaking to [~jason.greene] and [~brian.stansberry] it turned out that adding this deployment to our standard configs adds 2 seconds to boot time.
was (Author: kabirkhan):
The pull request was merged and then reverted. After speaking to [~jason.greene] and [~brian.stansberry] it turned out that adding this deployment to our standard configs, adds 2 seconds to boot time.
> Add WISE for Web console access
> -------------------------------
>
> Key: WFLY-6779
> URL: https://issues.jboss.org/browse/WFLY-6779
> Project: WildFly
> Issue Type: Feature Request
> Components: Web Console
> Reporter: R Searls
> Assignee: R Searls
> Priority: Minor
> Fix For: 11.0.0.Alpha1
>
>
> Wise is a Java framework for easily invoking webservices, which can be used as base for zero-code webservice invocation applications. (see http://wise.jboss.org/)
> Based upon Brian Stansberry's advise WISE is added to wfly using the "Mixed-Approach"
> for adding a feature.
> Once this is available in wfly. HAL can provide a link to it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (WFCORE-1738) Hint when versions are out-of-date pending restart
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1738?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky commented on WFCORE-1738:
-------------------------------------------
The CLI cannot know what will change after the restart, it cannot warn you about that. The output of the patch command does indicate that the server is in the restart-required state. Until you restart the server will not change its identity and will keep indicating to the management tools its current identity.
> Hint when versions are out-of-date pending restart
> --------------------------------------------------
>
> Key: WFCORE-1738
> URL: https://issues.jboss.org/browse/WFCORE-1738
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Patching
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
> Priority: Optional
>
> I have a minor usability suggestion. It's merely informational but I think helpful.
> When I was in the CLI tool to apply a version update patch (7.0.0 -> 7.0.1), I wasn't yet aware that I needed to restart the server for it to take effect. So when I afterward typed "version" to confirm the expected version bumps... well, they did not. I was specifically looking to confirm a change in both fields "JBoss AS release" and "JBoss AS product". With that said, it would be useful to add something to the output indicating the information being displayed will no longer be true.
> Illustrated example. Notice the asterisks:
> {code}
> JBOSS_HOME: C:\dev\jboss-eap-7
> JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"(*)
> JBoss AS product: JBoss EAP 7.0.0.GA(*)
> JAVA_HOME: c:\java\jdk1.8.0_45
> java.version: 1.8.0_45
> java.vm.vendor: Oracle Corporation
> java.vm.version: 25.45-b02
> os.name: Windows 7
> os.version: 6.1
> (*) Versions subject to change after patch takes effect at restart.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (WFLY-6617) Cannot inject session bean with @EJB to JSF PhaseListener
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-6617?page=com.atlassian.jira.plugin.... ]
Dmitrii Tikhomirov reassigned WFLY-6617:
----------------------------------------
Assignee: Dmitrii Tikhomirov (was: Farah Juma)
> Cannot inject session bean with @EJB to JSF PhaseListener
> ---------------------------------------------------------
>
> Key: WFLY-6617
> URL: https://issues.jboss.org/browse/WFLY-6617
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 10.0.0.Final
> Reporter: Tomas Remes
> Assignee: Dmitrii Tikhomirov
>
> Having something like following:
> {code}
> public class TestPhaseListener implements PhaseListener{
> @EJB
> TestEJB testEJB;
> ....
> }
> {code}
> result to null. Note that CDI injection works. Reading {{5.4.1
> JSF Managed Classes and Java EE Annotations}} in JSF spec I think this should work as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (WFLY-6966) FatalError on Transaction Expired Entry Monitor during server shutdown
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-6966?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated WFLY-6966:
--------------------------------
Issue Type: Enhancement (was: Bug)
> 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
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (WFCORE-1738) Hint when versions are out-of-date pending restart
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1738?page=com.atlassian.jira.plugi... ]
Marek Kopecký edited comment on WFCORE-1738 at 8/30/16 9:46 AM:
----------------------------------------------------------------
Sure.
Command for apply the patch: {{patch apply ../../jboss-eap-7.0.1-patch.zip}}
Command for get version info: {{version}}
Example of logs:
{noformat}
[mkopecky@localhost bin]$ ./jboss-cli.sh -c
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.0.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] patch apply ../../jboss-eap-7.0.1-patch.zip
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :shutdown(restart=true)
{"outcome" => "success"}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.6.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.1.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /]
{noformat}
was (Author: mkopecky):
Sure.
Command for apply the patch: {{patch apply ../../jboss-eap-7.0.1-patch.zip}}
Command for get version info: version
Example of logs:
{noformat}
[mkopecky@localhost bin]$ ./jboss-cli.sh -c
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.0.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] patch apply ../../jboss-eap-7.0.1-patch.zip
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :shutdown(restart=true)
{"outcome" => "success"}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.6.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.1.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /]
{noformat}
> Hint when versions are out-of-date pending restart
> --------------------------------------------------
>
> Key: WFCORE-1738
> URL: https://issues.jboss.org/browse/WFCORE-1738
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Patching
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
> Priority: Optional
>
> I have a minor usability suggestion. It's merely informational but I think helpful.
> When I was in the CLI tool to apply a version update patch (7.0.0 -> 7.0.1), I wasn't yet aware that I needed to restart the server for it to take effect. So when I afterward typed "version" to confirm the expected version bumps... well, they did not. I was specifically looking to confirm a change in both fields "JBoss AS release" and "JBoss AS product". With that said, it would be useful to add something to the output indicating the information being displayed will no longer be true.
> Illustrated example. Notice the asterisks:
> {code}
> JBOSS_HOME: C:\dev\jboss-eap-7
> JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"(*)
> JBoss AS product: JBoss EAP 7.0.0.GA(*)
> JAVA_HOME: c:\java\jdk1.8.0_45
> java.version: 1.8.0_45
> java.vm.vendor: Oracle Corporation
> java.vm.version: 25.45-b02
> os.name: Windows 7
> os.version: 6.1
> (*) Versions subject to change after patch takes effect at restart.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (WFCORE-1738) Hint when versions are out-of-date pending restart
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1738?page=com.atlassian.jira.plugi... ]
Marek Kopecký commented on WFCORE-1738:
---------------------------------------
Sure.
Command for apply the patch: {{patch apply ../../jboss-eap-7.0.1-patch.zip}}
Command for get version info: version
Example of logs:
{noformat}
[mkopecky@localhost bin]$ ./jboss-cli.sh -c
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.0.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] patch apply ../../jboss-eap-7.0.1-patch.zip
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.2.Final-redhat-1 "Kenny" // TODO
JBoss AS product: JBoss EAP 7.0.0.GA // TODO
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /] :shutdown(restart=true)
{"outcome" => "success"}
[standalone@localhost:9990 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /home/mkopecky/erase4/jboss-eap-7.0
JBoss AS release: 2.1.6.Final-redhat-1 "Kenny"
JBoss AS product: JBoss EAP 7.0.1.GA
JAVA_HOME: null
java.version: 1.8.0_91
java.vm.vendor: Oracle Corporation
java.vm.version: 25.91-b14
os.name: Linux
os.version: 4.4.14-200.fc22.x86_64
[standalone@localhost:9990 /]
{noformat}
> Hint when versions are out-of-date pending restart
> --------------------------------------------------
>
> Key: WFCORE-1738
> URL: https://issues.jboss.org/browse/WFCORE-1738
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Patching
> Reporter: Marek Kopecký
> Assignee: Alexey Loubyansky
> Priority: Optional
>
> I have a minor usability suggestion. It's merely informational but I think helpful.
> When I was in the CLI tool to apply a version update patch (7.0.0 -> 7.0.1), I wasn't yet aware that I needed to restart the server for it to take effect. So when I afterward typed "version" to confirm the expected version bumps... well, they did not. I was specifically looking to confirm a change in both fields "JBoss AS release" and "JBoss AS product". With that said, it would be useful to add something to the output indicating the information being displayed will no longer be true.
> Illustrated example. Notice the asterisks:
> {code}
> JBOSS_HOME: C:\dev\jboss-eap-7
> JBoss AS release: 2.1.2.Final-redhat-1 "Kenny"(*)
> JBoss AS product: JBoss EAP 7.0.0.GA(*)
> JAVA_HOME: c:\java\jdk1.8.0_45
> java.version: 1.8.0_45
> java.vm.vendor: Oracle Corporation
> java.vm.version: 25.45-b02
> os.name: Windows 7
> os.version: 6.1
> (*) Versions subject to change after patch takes effect at restart.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month