Skip to main content

iphone5 charger cable worse quality I have seen

The lightning cable broke within a month. I was on trip to Houston and in the car it will start charging and then die. Then I went to hotel and put it on wall plug and it wont charge. I had a suspicion that putting it in car confused the phone but restart wont help. I remember 2-3 days back it would charge and 90% and then say accessory not supported. I thought its some bug in new update.

So I went to walmart in Houston at 9:00 in night on a trip to NASA and then got a cable, while I was checking out I found one more customer came asking for iphone lightning charger cable, I was now sure its a cable issue.  So I bought the cable went to hotel and this also wont charge, I went again and got another cable and that one worked.  What a bummer I thought the phone went bad.

Three days after I came back home I called AT&T to send me a replacement cable and they sent me their own proprietary cable which means even they know that the OEM cable by Apple sucks and they charge $30-$40 for it. No wonder walmart guy was telling me not to waste money on it and buy the $15 off the shelf non OEM cable.

Anyways the AT&T cable looks sturdy so far.


Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost(""); factory.setPort(5672); Conne…

What a rocky start to labor day weekend

Woke up by earthquake at 7:00 AM in morning and then couldn't get to sleep. I took a bath, made my tea and started checking emails and saw that after last night deployment three storage node out of 100s of nodes were running into Full GC. What was special about the 3 nodes was that each one was in a different Data centre but it was named same app02.  This got me curious I asked the node to be taken out of rotation and take a heap dump.  Yesterday night a new release has happened and I had upgraded spymemcached library version as new relic now natively supports instrumentation on it so it was a suspect. And the hunch was a bullseye, the heap dump clearly showed it taking 1.3G and full GCs were taking 6 sec but not claiming anything.

I have a quartz job in each jvm that takes a thread dump every 5 minutes and saves last 300 of them, checking few of them quickly showed a common thread among all 3 data centres. It seems there was a long running job that was trying to replicate pending…

Spring query timeout or transaction timeout

If you are using spring to manage transactions then you can specify default transaction timeout using

    <bean id="transactionManager"
        <property name="dataSource" ref="dataSource" />
        <property name="defaultTimeout" value="30" /> <!--30 sec--->             

or you can override the timeout in the annotation

    @Transactional(readOnly = false, timeout=30)

or if you are doing it programatic transactions then you can do

DataSourceTransactionManager transactionManager = new DataSourceTransactionManager(dataSource);

 or you can override the timeout for one particular transaction

TransactionTemplate transactionTemplate = new TransactionTemplate();