Archive for the ‘Uncategorized’ Category

Safe to say walmart uses …. Spring, Tomcat and …

Friday, September 25th, 2009

https://www.walmart.com/subflow/YourAccountLoginContext/###/sub_generic_login/loginModule.do?prefix=/site_login&page=/ProcessLogin.do

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

com.wm.weblib.sys.UserSessionExpiredException: WebFlowMap is missing in session.
com.wm.weblib.webflow.Subflow2005Servlet.service(Subflow2005Servlet.java:140)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
com.wm.weblib.util.ResourceExpositionFilter.doFilter(ResourceExpositionFilter.java:52)
com.wm.weblib.pa.response.ResponseMinificationFilter.doFilter(ResponseMinificationFilter.java:47)
com.wm.weblib.pa.response.ResponseCacheFilter.doFilter(ResponseCacheFilter.java:69)
com.wm.www.apps.pharmacy.action.ServicesAccessFilter.doFilter(ServicesAccessFilter.java:130)
com.wm.www.apps.swap.util.CustomerDataCookieFilter.doFilter(CustomerDataCookieFilter.java:69)
org.apache.tomcat.filters.WMReflectorFilter.doFilter(WMReflectorFilter.java:79)
com.wm.www.handler.csb.ContinueShoppingButtonFilter.doFilter(ContinueShoppingButtonFilter.java:73)
com.wm.www.ppc.util.PPCFilter.doFilterInternal(PPCFilter.java:119)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
org.owasp.stinger.StingerFilter.doFilter(Unknown Source)
com.wm.weblib.util.RedirectForwardIncludeLoggingFilter.doFilter(RedirectForwardIncludeLoggingFilter.java:57)
org.apache.tomcat.filters.WMReportingFilter.doFilter(WMReportingFilter.java:78)
com.wm.weblib.util.NextProductToBuyFilter.doFilter(NextProductToBuyFilter.java:70)
com.wm.weblib.natsearch.NaturalSearchFilter.doFilter(NaturalSearchFilter.java:85)
com.wm.weblib.util.BrowserPreference$Filter.doFilter(BrowserPreference.java:645)
com.wm.weblib.util.BrowserPreferenceFilter.doFilter(BrowserPreferenceFilter.java:8)
com.wm.weblib.sys.XFilter.doFilter(XFilter.java:50)
com.wm.weblib.psl.SessionFilter.doFilter(SessionFilter.java:87)
com.wm.weblib.cookies.AbstractCookieFilter.doFilter(AbstractCookieFilter.java:179)
com.wm.weblib.cookies.AbstractCookieFilter.doFilter(AbstractCookieFilter.java:179)
org.apache.tomcat.filters.URIRedirectFilter.doFilter(URIRedirectFilter.java:100)
com.wm.weblib.util.RequestEnvironmentFilter.doFilter(RequestEnvironmentFilter.java:25)
com.wm.weblib.gs.GracefulShutdownFilter.doFilter(GracefulShutdownFilter.java:80)
org.apache.tomcat.filters.WMTimerFilter.doFilter(WMTimerFilter.java:103)

note The full stack trace of the root cause is available in the Apache Tomcat/5.5.23 logs.

Some Title Any

Tuesday, May 20th, 2008

Verify
Technorati Profile

MQ Series 6 on Ubuntu

Thursday, April 17th, 2008

This is just a quick post about installing MQ on Ubuntu. Since Hardy is coming out in less than a week I’ll need to do it again.

Install rpm

*Your mount steps may vary.

mkdir tmp-mq
sudo mount -t iso9660 -r -o loop /media/FIRELITE/ISO/WMQ_600.iso ~/tmp-mq/
./mqlicense.sh
rpm -ivh –nodeps MQSeriesRuntime-6.0.0-0.i386.rpm
rpm -ivh –nodeps MQSeriesServer-6.0.0-0.i386.rpm
rpm -ivh –nodeps MQSeriesJava-6.0.0-0.i386.rpm
rpm -ivh –nodeps MQSeriesSamples-6.0.0-0.i386.rpm
rpm -ivh –nodeps MQSeriesMan-6.0.0-0.i386.rpm
rpm -ivh –nodeps MQSeriesIES30-6.0.0-0.i386.rpm
rpm -ivh –nodeps MQSeriesConfig-6.0.0-0.i386.rpm

Rinse and repeat the steps above for the patches from IBM.

su - mqm from root

Create a Queue Manager :

crtmqm TEST

Configure:
strmqcfg -c

Add your self to the MQM Group.

You should be good to go.

Launching the MQ Explorer.

create a workspace in your home mine is called mq-ws

/opt/mqm/ies30/eclipse/.eclipse

Use the workspace you created in the above step.

You should be golden now. Much props to Nacho M. for the rpm stuff.

-Doyle

Incremental code review (ICR)

Thursday, February 7th, 2008

I suggested that we start doing weekly code reviews on two projects that I’m currently developing on. So we are on week three of one and week one of another. This is a break from the norm where we normally do the code reviews when we are done coding. I’ve been screaming for incremental code reviews for along time.

Some Do’s:

  1. Have the review at least once a week when coding heavy.
  2. Do include the designer or the business expert. (We have caught minor and major items before they became bugs/defects!)
  3. Everyone takes turns showing their code.
  4. Check the egos and the clubs at the door.
  5. Use a separate machine not the developers machine. You  will be surprised at what you find or don’t.
  6. Make sure the machine has access to your CVS or whatever you are using. That way comments and code changes are checked in when you are done with the code review. Never let anyone take a note to change it later.
  7. Ask questions.

Benefits:

  1. Better team and code cohesion.
  2. Catching bugs early in the design.
  3. A true status of where we are.
  4. Pressure to keep the code in synch all the time.

That’s about it for right now. We have caught some holes in the design that would not have been caught until test. I think anyone can apply ICR to whatever methodology the subscribe to e.g. waterfall , agile … etc. We also seem to have a more complete earlier?

I guess I should add that one team has four and the other has three.

Don’t do the review if you don’t have the business people involved.

Refactoring Even Faster …. with method draging in eclipse ….

Thursday, January 10th, 2008

Today I was doing some refactoring in RAD (Rational Application Developer) and found my self looking over in the package explorer thinking gee I’ll have to move that method over to the class I just created to get rid of the two classes I’m factoring out. I looked over and thought I should be able to just drag it down into the other class. BAM like a champ when I grabbed that green orb it moved right over when I plopped it down on the new class, updated all the reference just like I would have done it via ALT+SHIFT+V and navigate around to the class I wanted it to go. Normally I’m a keyboard Jedi but I guess I’ll be making an exception.

Home page … revamp

Tuesday, December 11th, 2007

Finally added the hook from my home page to my blog. This should be much better now. Have to fix the special characters … things to do things to do.

It’s over for the home button … Browser Consolidation

Thursday, December 6th, 2007

Yeah… I killed the home button on my browser. I never use it. If I really want to go home I’ll just use the ctrl + home key. Also, moved location to the top level. Saving myself a few pixels in height.small-fox

Tie a napkin around that coffee handle … ?

Thursday, November 8th, 2007

What’s the deal with tying a napkin around the coffee pot handle? What does this mean? Does it mean that the coffee is no good, are you cleaning the pot, is it god forbid decaf (I use the orange pot for regular coffee if I have to make it). Seriously, I need to know what this mean! All I know is that every time I see that pot with that napkin it smells like starbucks. I hope you don’t mind that I poor it into the orange pot and brew the marked coffee with regular coffee.

You know you could just get some tape and tell me what is in the pot. Just in case it’s not the star-crack.

Can we talk about the lack of donuts ….

Oracle 10g XE Universal on Ubuntu 7.10

Wednesday, November 7th, 2007

I just want to say straight out that the forum and user dos on the Oracle are fantastic. Tons of information and very straight forward.

The package installs very cleanly.

The only thing is to do is add yourself to the dba group.

More than a Passing comment about Licensing Programmers to do work

Thursday, July 26th, 2007

This is a response to a very frustrated and thoughtful post by Scott H.

Scott talks about Licensing Programmers to do work and how recruiters are gun-decking resumes. (And they do) Sure a license is great but I think in this industry we have a very unique opportunity to see if someone can program. It might be difficult to get a civil engineer to build a bridge in an interview on the other hand.

At the place I work we have candidates write code.  Wow mind blowing. You can either do it or not. Now here is how I set it up.

Resume of gets handed to me from our recruiting staff. I read it. Wow five years of experience and  400 technologies later. Call the candidate.  Give him a brief about us and ask why you want to work here yada yada. Now I send him some code to implement, if the call went well. We are about 74% a java shop. So I send a jUnit xyzTest out zipped up in an eclipse project ask that they implement the code to make the test pass. They send it back. I look at the code check the pass fail. You can tell a lot about a person about the code they write. Long variable names, understandable method name, uses encapsulation, and  the list goes on. Personally I think code is very personal since this is your creation, if not I don’t want to work with you.

If all went well, I call him/her in. We set up a team interview. Then we do a code review in the interview. This is where we check the communication skills and how well they take constructive criticism. Next we ask them to code a similar problem. This is where we get to see if they can really code and understand the problem. Yes, we let candidate use industry tools for the exerciser. If eclipse, net beans, or vi is on your resume then we will set that up. We hired a guy who asked if he could use the internet to look something up!

If you know hibernate then we have a test for you. If it’s on your resume we test for it. Most not all of our stuff is very straight forward, no tricks, no corner cases. You either know it or you don’t.

Example: You worked for xyz bank we have a problem that by using BigDecimal you would be done in under 2 minuets. If you worked with money then there is a high likely hood you have used this class. Yes, you can still solve the problem with out BigDecimal but it will take longer. Then we will know where you stand.

Some people refuse to write code in the interview. We don’t hire them. Some people can’t finish the problem but they write the code anyway. We help them out as they need it. We have hired most of our junior programmers this way. You know quality, creativity and passion when you see it.

Once that gets around the recruiters stop sending you crap.

If you think this is mean then re-read the blog article listed at the top of the page.