kill activemq

error:

java.io.IOException: Transport Connector could not be registered in JMX: java.io.IOException: Failed to bind to server socket due to: java.net.BindException: Address already in use: JVM_Bind

eg:

netstat -a -o -n | findstr 616
  TCP    127.0.0.1:61616        127.0.0.1:61616        ESTABLISHED     20816

taskkill /F /PID 20816
SUCCESS: The process with PID 20816 has been terminated.

Resolved: Springboot & Htmlunit hit error: IllegalArgumentException Not supported http://javax.xml.XMLConstants/property/accessExternalDTD

 

Springboot & Htmlunit hit error: Caused by: java.lang.IllegalArgumentException: Not supported: http://javax.xml.XMLConstants/property/accessExternalDTD

Logs:

15:46:07.782|INFO |

Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled.|main|org.springframework.boot.autoconfigure.logging.AutoConfigurationReportLoggingInitializer

15:46:07.792|ERROR|Application startup failed|main|org.springframework.boot.SpringApplication

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'payloadRootAnnotationMethodEndpointMapping' defined in class path resource [org/springframework/ws/config/annotation/DelegatingWsConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.ws.server.endpoint.mapping.PayloadRootAnnotationMethodEndpointMapping]: Factory method 'payloadRootAnnotationMethodEndpointMapping' threw exception; nested exception is java.lang.ExceptionInInitializerError

at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1178) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1072) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:511) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867) ~[spring-context-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543) ~[spring-context-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693) ~[spring-boot-1.5.19.RELEASE.jar:1.5.19.RELEASE]

at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360) ~[spring-boot-1.5.19.RELEASE.jar:1.5.19.RELEASE]

at org.springframework.boot.SpringApplication.run(SpringApplication.java:303) ~[spring-boot-1.5.19.RELEASE.jar:1.5.19.RELEASE]

at org.springframework.boot.test.context.SpringBootContextLoader.loadContext(SpringBootContextLoader.java:121) [spring-boot-test-1.5.19.RELEASE.jar:1.5.19.RELEASE]

at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.web.ServletTestExecutionListener.setUpRequestContextIfNecessary(ServletTestExecutionListener.java:189) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.web.ServletTestExecutionListener.prepareTestInstance(ServletTestExecutionListener.java:131) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:230) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:228) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:287) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) [junit-4.12.jar:4.12]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:289) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:247) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12]

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12]

at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12]

at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12]

at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12]

at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:191) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:542) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:770) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:464) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:210) [.cp/:na]

Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.ws.server.endpoint.mapping.PayloadRootAnnotationMethodEndpointMapping]: Factory method 'payloadRootAnnotationMethodEndpointMapping' threw exception; nested exception is java.lang.ExceptionInInitializerError

at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

... 42 common frames omitted

Caused by: java.lang.ExceptionInInitializerError: null

at org.springframework.ws.config.annotation.WsConfigurationSupport.payloadRootAnnotationMethodEndpointMapping(WsConfigurationSupport.java:94) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

at org.springframework.ws.config.annotation.DelegatingWsConfiguration$$EnhancerBySpringCGLIB$$7f55e9f9.CGLIB$payloadRootAnnotationMethodEndpointMapping$4(<generated>) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

at org.springframework.ws.config.annotation.DelegatingWsConfiguration$$EnhancerBySpringCGLIB$$7f55e9f9$$FastClassBySpringCGLIB$$10aee995.invoke(<generated>) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) ~[spring-core-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) ~[spring-context-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.ws.config.annotation.DelegatingWsConfiguration$$EnhancerBySpringCGLIB$$7f55e9f9.payloadRootAnnotationMethodEndpointMapping(<generated>) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_265]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_265]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_265]

at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_265]

at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

... 43 common frames omitted

Caused by: java.lang.IllegalArgumentException: Not supported: http://javax.xml.XMLConstants/property/accessExternalDTD

at org.apache.xalan.processor.TransformerFactoryImpl.setAttribute(TransformerFactoryImpl.java:571) ~[xalan-2.7.2.jar:na]

at org.springframework.xml.transform.TransformerFactoryUtils.defaultSettings(TransformerFactoryUtils.java:56) ~[spring-xml-2.4.4.RELEASE.jar:na]

at org.springframework.xml.transform.TransformerFactoryUtils.newInstance(TransformerFactoryUtils.java:32) ~[spring-xml-2.4.4.RELEASE.jar:na]

at org.springframework.ws.server.endpoint.mapping.PayloadRootAnnotationMethodEndpointMapping.<clinit>(PayloadRootAnnotationMethodEndpointMapping.java:58) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

... 54 common frames omitted

15:46:07.794|ERROR|Caught exception while allowing TestExecutionListener [org.springframework.test.context.web.ServletTestExecutionListener@f2f2cc1] to prepare test instance [test.com.tiongnam.sync.sss.TestDownloadQuotation@403cff1c]|main|org.springframework.test.context.TestContextManager

java.lang.IllegalStateException: Failed to load ApplicationContext

at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:124) ~[spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83) ~[spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.web.ServletTestExecutionListener.setUpRequestContextIfNecessary(ServletTestExecutionListener.java:189) ~[spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.web.ServletTestExecutionListener.prepareTestInstance(ServletTestExecutionListener.java:131) ~[spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:230) ~[spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:228) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:287) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) [junit-4.12.jar:4.12]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:289) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:247) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12]

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12]

at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12]

at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12]

at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12]

at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:191) [spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:542) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:770) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:464) [.cp/:na]

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:210) [.cp/:na]

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'payloadRootAnnotationMethodEndpointMapping' defined in class path resource [org/springframework/ws/config/annotation/DelegatingWsConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.ws.server.endpoint.mapping.PayloadRootAnnotationMethodEndpointMapping]: Factory method 'payloadRootAnnotationMethodEndpointMapping' threw exception; nested exception is java.lang.ExceptionInInitializerError

at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1178) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1072) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:511) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867) ~[spring-context-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543) ~[spring-context-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693) ~[spring-boot-1.5.19.RELEASE.jar:1.5.19.RELEASE]

at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360) ~[spring-boot-1.5.19.RELEASE.jar:1.5.19.RELEASE]

at org.springframework.boot.SpringApplication.run(SpringApplication.java:303) ~[spring-boot-1.5.19.RELEASE.jar:1.5.19.RELEASE]

at org.springframework.boot.test.context.SpringBootContextLoader.loadContext(SpringBootContextLoader.java:121) ~[spring-boot-test-1.5.19.RELEASE.jar:1.5.19.RELEASE]

at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98) ~[spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116) ~[spring-test-4.3.22.RELEASE.jar:4.3.22.RELEASE]

... 25 common frames omitted

Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.ws.server.endpoint.mapping.PayloadRootAnnotationMethodEndpointMapping]: Factory method 'payloadRootAnnotationMethodEndpointMapping' threw exception; nested exception is java.lang.ExceptionInInitializerError

at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

... 42 common frames omitted

Caused by: java.lang.ExceptionInInitializerError: null

at org.springframework.ws.config.annotation.WsConfigurationSupport.payloadRootAnnotationMethodEndpointMapping(WsConfigurationSupport.java:94) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

at org.springframework.ws.config.annotation.DelegatingWsConfiguration$$EnhancerBySpringCGLIB$$7f55e9f9.CGLIB$payloadRootAnnotationMethodEndpointMapping$4(<generated>) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

at org.springframework.ws.config.annotation.DelegatingWsConfiguration$$EnhancerBySpringCGLIB$$7f55e9f9$$FastClassBySpringCGLIB$$10aee995.invoke(<generated>) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) ~[spring-core-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:358) ~[spring-context-4.3.22.RELEASE.jar:4.3.22.RELEASE]

at org.springframework.ws.config.annotation.DelegatingWsConfiguration$$EnhancerBySpringCGLIB$$7f55e9f9.payloadRootAnnotationMethodEndpointMapping(<generated>) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_265]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_265]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_265]

at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_265]

at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162) ~[spring-beans-4.3.22.RELEASE.jar:4.3.22.RELEASE]

... 43 common frames omitted

Caused by: java.lang.IllegalArgumentException: Not supported: http://javax.xml.XMLConstants/property/accessExternalDTD

at org.apache.xalan.processor.TransformerFactoryImpl.setAttribute(TransformerFactoryImpl.java:571) ~[xalan-2.7.2.jar:na]

at org.springframework.xml.transform.TransformerFactoryUtils.defaultSettings(TransformerFactoryUtils.java:56) ~[spring-xml-2.4.4.RELEASE.jar:na]

at org.springframework.xml.transform.TransformerFactoryUtils.newInstance(TransformerFactoryUtils.java:32) ~[spring-xml-2.4.4.RELEASE.jar:na]

at org.springframework.ws.server.endpoint.mapping.PayloadRootAnnotationMethodEndpointMapping.<clinit>(PayloadRootAnnotationMethodEndpointMapping.java:58) ~[spring-ws-core-2.4.4.RELEASE.jar:na]

... 54 common frames omitted

Resolved by:

In Debug/Run Configurations

Adding 

-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl

into VM arguments 

 

References:

How to pass the -D System properties while testing on Eclipse?

https://stackoverflow.com/a/862405

Unknown attribute accessExternalDTD while creating Spring bean

https://stackoverflow.com/a/64047443

What's is better wear level?

Searched: what is battery wear level

Reference URL: https://forums.tomsguide.com/threads/battery-wear-level-problems.395424/

Dec 27, 2015

• #2

As a battery gets older, it loses capacity. If the battery's capacity when new was 4000 mAh, and its current capacity is only 3600 mAh (90% of new), then it has a battery wear level of 10%.

That said, battery wear is mostly caused by deep charge cycles. That is, charging to 100% and discharging to 0%. Shallow cycles (say, charging to 70% and discharging to 30% put almost no wear on the battery.

http/batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

Newer laptops (and phones, and electric vehicles) are programmed not to fully charge nor discharge the battery in order to prevent wear and maintain battery longevity. One of the ways I've seen some devices do this is by "faking out" Windows into thinking the battery has more wear than it really does. So the battery may be 4000 mAh when new, but the battery tells Windows it has 10% wear. This prevents Windows from charging it past 90%, thus preventing a deep cycle.

This is just one of the wear-prevention strategies out there, and I don't know if the ASUS X205TA is using it. So it could just be reporting a fake wear level to Windows. OTOH if the original owner let the battery discharge completely and left it that way, it may have self-discharged past 0% enough to damage the battery and the reported wear level may be accurate.

The only true test will be to monitor the wear level over several months of use. If it holds steady between 15%-20%, then it's probably nothing to worry about. If it continues wearing quickly, then the battery may have been damaged by the previous owner. (Measuring battery capacity and wear level is a bit of a black art, as it requires extremely accurate measurements of voltage. Things like discharge rate and temperature can drastically change the results, so a +/- 3% change in wear level day-to-day is not unusual.)

What is the 1st thing to do after check out angular project from git?

 

What is the 1st thing to do after check out angular project from git?

Reference URL: https://stackoverflow.com/a/54142081



npm install

Extract some pages from a PDF file with Foxit free?

 

Foxit doesn't have this feature.

But found this workaround from foxit forum.

Source URL: https://forums.foxitsoftware.com/forum/portable-document-format-pdf-tools/foxit-reader/33530-how-to-delete-document-page-in-foxit-reader-free

05-16-2015, 08:31 PM

Actually you can easily delete pages on the FoxIt Free version. Here is how:

1) Make sure you have FoxIt Reader PDF Printer installed
2) Click the printer icon or press control P while viewing your PDF
3) Select "FoxIt Reader PDF Printer" as your printer from the drop-down menu
4) Select the "Pages" radio box and enter the pages you want in your PDF (in your case enter "2-3")
5) A new PDF will now be generated containing only the pages you specified, effectively deleting the other pages from your PDF

Blocking .Net Framework 4.7 installations?

 

Source URL: https://dotnet.microsoft.com/download/dotnet-framework/net35-sp1

MARTIN BRINKMANN

Jun 12, 2017

Windows

|

10

Windows users who don't want the Microsoft .NET Framework 4.7 at this point in time may block the Windows Update deployment of it.

Microsoft released the new .Net Framework 4.7 back in April 2017, and announced back then that it would distribute the new version "in a couple of months" through Windows Update.

Anyone interested in the new version could download online and offline installers for the .Net Framework 4.7 already.

The new version introduces new capabilities to the framework which users will benefit from as well once they are integrated into .Net applications. This includes high DPI support for Windows Forms, touch support for WPF applications, performance and reliability improvements, and enhanced cryptography support.

The new version is an in-place upgrade for the following .Net Framework versions: 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2.

Note: The Microsoft .Net Framework 4.7 is part of The Windows 10 Creators Update. If you run that particular version of Windows 10, you are all set already.

Blocking the .Net Framework 4.7

Microsoft notes in a new support article that some businesses and organizations may have the requirement to block the installation of the new .Net Framework version for a temporary period of time.

Provided through Windows Update and Windows Server Update Service (WSUS), the .Net Framework 4.7 is offered as a recommended update on all platforms that Microsoft released it for.

Windows administrators who want to block the deployment of the latest version of the .Net Framework need to set a Registry key for that. While there may be other means to do that, hiding the update in Windows Update, or using manual updating methods only, this is the recommended method by Microsoft.

1. Tap on the Windows-key, type regedit.exe, and hit the Enter-key on the keyboard. This should start the Windows Registry Editor.
2. Go to the key: HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP
3. Right-click on NDP and select New > Key.
4. Name that key WU.
5. Right-click on WU, and select New > Dword (32-bit) Value.
6. Name it BlockNetFramework47.
7. Set its value to 1 (double-click it to set value).

Microsoft admits in the support article that this is a temporary block. The company has yet to reveal for how long it will block the deployment of the new .Net Framework.

We will update this article once Microsoft communicates the deadline.

Tip: Use the .Net Framework 4.7 Cleanup Tool to remove versions completely from your system.

ActiveMQ couldn't start.

 


java.net.BindException: Address already in use: JVM_Bind


resolved by turn off device's Mobile Hotspot

Reference URL: https://stackoverflow.com/a/17694754

If you are using Windows 7, please try to disable "Internet Connection Sharing (ICS)" service.

Angular pipe could not be found

 

Angular pipe could not be found

Reference URL: https://stackoverflow.com/a/40463405

see this is working for me.

ActStatus.pipe.ts First this is my pipe

import {Pipe,PipeTransform} from "@angular/core"; @Pipe({ name:'actStatusPipe' }) export class ActStatusPipe implements PipeTransform{ transform(status:any):any{ switch (status) { case 1: return "UN_PUBLISH"; case 2: return "PUBLISH"; default: return status } } }

main-pipe.module.ts in pipe module, i need to declare my pipe/s and export it.

import { NgModule } from '@angular/core'; import {CommonModule} from "@angular/common"; import {ActStatusPipe} from "./ActStatusPipe.pipe"; // <--- @NgModule({ declarations:[ActStatusPipe], // <--- imports:[CommonModule], exports:[ActStatusPipe] // <--- }) export class MainPipe{}

app.module.ts user this pipe module in any module.

@NgModule({ declarations: [...], imports: [..., MainPipe], // <--- providers: [...], bootstrap: [AppComponent] })

you can directly user pipe in this module. but if you feel that your pipe is used with in more than one component i suggest you to follow my approach.

1. create pipe .

2. create separate module and declare and export one or more pipe.

3. user that pipe module.

How to use pipe totally depends on your project complexity and requirement. you might have just one pipe which used only once in the whole project. in that case you can directly use it without creating a pipe/s module (module approach).

gzip with -9 option

 
A log file: with size of: 789M

gzip with different option, to have different compression as below

gzip -9 file.log

32M

gzip -9 file.log

37MB

example #2

-rw-r--r--. 1 srvusr srvusr  87M Jul 18 19:53 output.log.20220718_pm074234.log

-rw-r--r--. 1 root   root    87M Jul 21 12:01 output.log.20220718_pm074234.without9.log

sudo gzip -9 output.log.20220718_pm074234.log

sudo gzip output.log.20220718_pm074234.without9.log

-rw-r--r--. 1 srvusr srvusr 4.0M Jul 18 19:53 output.log.20220718_pm074234.log.gz

-rw-r--r--. 1 root   root   4.2M Jul 21 12:01 output.log.20220718_pm074234.without9.log.gz

Export connections in MySQL Workbench

saw in log:

%USERPROFILE%\AppData\Roaming\MySQL\Workbench\connections.xml


cd %USERPROFILE%\AppData\Roaming\MySQL\
zip up whole folder: Workbench

restore in new laptop, and done.

you can get what you have in previous laptop, the price to pay so far is: rekey in all passwords for all connections.

Subversive vs Subclipse

 

Found a chinese article sharing his experience as per title.

从 Subclipse 到 Subversive: 第一印象

Source URL; https://cumt.org/blog/550

His preference is: Subversive.

I never run into any issue among these, Subversive vs Subclipse before version 2020-09, until 2021-06 tested with Subclipse.

Eclipse 2021-09 unable install Subversive - SVN Team Provider 4.0.5

 

"The following solutions are not available: Subversive - SVN Team provider 4.0.5"

Version: 2021-09

The following solutions are not available: Subversive - SVN Team Provider 4.0.5 (id=org.eclipse.team.svn.resource.ignore.rules.jdt.feature.group, site=http://download.eclipse.org/technology/subversive/4.0/update-site/)

Version: 2021-06

The following solutions are not available: Subversive - SVN Team Provider 4.0.5 (id=org.eclipse.team.svn.resource.ignore.rules.jdt.feature.group, site=http://download.eclipse.org/technology/subversive/4.0/update-site/)

but URL still reachable via browser: http://download.eclipse.org/technology/subversive/4.0/update-site/

So I manual add to install with Eclipse@202109.

For later versions: 

SVN with eclipse 2022-09
https://billson.blogspot.com/2022/10/svn-with-eclipse-2022-09.html

SVN with eclipse 2022-12 R & 2023-06 R

https://billson.blogspot.com/2023/03/svn-with-eclipse-2022-12.html

Archived: How to clear the 'SoftwareDistribution' folder on Windows 10 and make updates happen again

 

WINDOWS 10 ADVANCED

How to clear the 'SoftwareDistribution' folder on Windows 10 and make updates happen again

If Windows Update isn't working, it could be caused by a problem with the SoftwareDistribution folder, and here we'll show you how to fix it.

MAURO HUCULAK

16 Mar 2017

On Windows 10, the "SoftwareDistribution" folder is an essential component for Windows Update, which temporarily stores files needed to install new updates to keep your device secure and with the latest fixes and improvements.

This folder is maintained by the WUAgent (Windows Update Agent), and typically, it should be left alone, but there will be times when you may need to clear its content manually in the case the Datastore and Download folders aren't synchronized, and it's preventing Windows Update from applying new updates to your PC.

Usually, if you're having trouble with Windows Update, or after updates have been applied, it's safe to empty the content of the SoftwareDistribution folder. Windows 10 will always re-download all the necessary files, or re-create the folder and re-download all the components, if removed.

In this Windows 10 guide, we'll walk you through the steps to delete the content inside the SoftwareDistribution folder. As an alternative option, we'll also show you the steps to rename the folder, in case you only want to test if the folder's content is the one causing problems.

• How to clear the 'SoftwareDistribution' folder
• How to rename the 'SoftwareDistribution' folder

How to clear the 'SoftwareDistribution' folder

To delete the content inside the SoftwareDistribution folder, do the following:

1. Open Start.
2. Search for Command Prompt, right-click the result, and select Run as administrator.

3. Type the following command to stop the Windows Update Service and press Enter:

   net stop wuauserv

4. Type the following command to stop the Background Intelligent Transfer Service and press Enter:

   net stop bits

   

5. Use the Windows key + R keyboard shortcut to open the Run command.

6. Open File Explorer and browse the following path:

   C:\Windows\SoftwareDistribution

7. Select all its content and click the Delete button to clear the content.

   

   Quick Tip: In the case, you're having trouble deleting all the files, simply restart your computer, and try again.

8. On Command Prompt, type the following command to start the Windows Update Service and press Enter:

   net start wuauserv

9. Type the following command to start the Background Intelligent Transfer Service and press Enter:

   net start bits

   

Once you completed the steps, Windows 10 will reconfigure the folder and re-download all the necessary components.

How to rename the 'SoftwareDistribution' folder

If you don't want to delete the content inside of the folder, you can alternatively, rename the folder to troubleshoot Windows Update problems.

To rename the SoftwareDistribution folder, do the following:

1. Open Start.
2. Search for Command Prompt, right-click the result, and select Run as administrator.

3. Type the following command to stop the Windows Update Service and press Enter:

   net stop wuauserv

4. Type the following command to stop the Background Intelligent Transfer Service and press Enter:

   net stop bits

   

5. Use the Windows key + R keyboard shortcut to open the Run command.

6. Type the following command to rename the folder and press Enter:

   rename %windir%\SoftwareDistribution SoftwareDistribution.bak

   

   Quick Tip: If the command isn't letting you rename the folder, try steps No. 3 and 4 one more time, and then try to rename the folder.

7. Type the following command to start the Windows Update Service and press Enter:

   net start wuauserv

8. Type the following command to start the Background Intelligent Transfer Service and press Enter:

   net start bits

   

After you've completed the steps, Windows 10 will re-create the folder and re-download all the necessary components.

The only caveat with this process is that the SoftwareDistribution folder also includes the Windows Update history information, which means that emptying up the folder will result in loss of this data. In addition, you'll notice that Windows Update will take longer than usual to detect and update your computer because the WUAgent must check and re-create the Datastore information. However, it's a small price to pay to get your device to update again.

While sometimes the folder may grow, it's only recommended to use these instructions only when necessary. You shouldn't mess with the SoftwareDistribution folder to free up storage space on your computer.