Spring Boot and JBOSS EAP 6.2.0 logging
Problem: There is no logging with Java jax-ws client. Other logs are written fine to server.log
logback.xml
PUSH: | |
* tar cvf - . | gzip -c -1 | ssh user@host cat ">" remotefile.gz | |
* ssh target_address cat <localfile ">" remotefile | |
* ssh target_address cat <localfile - ">" remotefile | |
* cat localfile | ssh target_address cat ">" remotefile |
@Bean | |
EmbeddedServletContainerCustomizer containerCustomizer( | |
@Value("${keystore.file}") Resource keystoreFile, | |
@Value("${keystore.pass}") String keystorePass) throws Exception { | |
String absoluteKeystoreFile = keystoreFile.getFile().getAbsolutePath(); | |
return (ConfigurableEmbeddedServletContainer container) -> { | |
if (container instanceof TomcatEmbeddedServletContainerFactory) { |
Problem: There is no logging with Java jax-ws client. Other logs are written fine to server.log
import oracle.ons.ONS; | |
import oracle.ons.SenderThread; | |
import org.slf4j.Logger; | |
import org.slf4j.LoggerFactory; | |
import org.springframework.util.ReflectionUtils; | |
import javax.management.MBeanServer; | |
import javax.management.ObjectName; | |
import javax.servlet.ServletContextEvent; | |
import javax.servlet.ServletContextListener; |
Setup:
$ mongo
> use pubsub
> db.createCollection('messages', { capped: true, size: 100000 })
> db.messages.insert({})
#Container Resource Allocation Options in docker-run You have various options for controlling resources (cpu, memory, disk) in docker. These are principally via the docker-run command options.
##Dynamic CPU Allocation
-c, --cpu-shares=0
CPU shares (relative weight, specify some numeric value which is used to allocate relative cpu share)
##Reserved CPU Allocation
echo "Type your email, followed by [ENTER]:" | |
read email | |
find . -maxdepth 1 -type d \( ! -name . \) -exec bash -c "cd '{}' && git config user.email $email" \; |
//: Check divisible by 3 and 5 with GameplayKit Rule System | |
import GameplayKit | |
let divisibleBy3Rule = GKRule(blockPredicate: { system in | |
(system.state["value"] as! Int) % 3 == 0 | |
}, action: { system in | |
system.assertFact("divisibleBy3and5", grade: 0.5) | |
system.assertFact("divisibleBy3", grade: 1) | |
}) |
//: Playground - noun: a place where people can play | |
import GameplayKit | |
class ShootingComponent: GKComponent { | |
let power: Int | |
init(power: Int) { | |
self.power = power |
Most of us won’t be able to use/deploy JDK 8 in production for a looong time. But that shouldn’t stop us from using it, right?
It should be possible to sneak in JDK 8 in the back way, the same way we snuck in Groovy and other libraries we wanted to use.
The Maven compiler plugin run in two separate lifecycles, compile and testCompile. Those can be configured separately.