Client doesn't seem to work. Keeps showing Loading... about alexandria

[ayende]

Enable logging, and see what is going on. Check for firewalls, in
particular.

On Fri, Jul 22, 2011 at 11:07 AM, ronsher <
[email protected]>wrote:

I've run the sql script.
I've run the backend side and verified the backend is listening.
I also see that the backend is receiving the client messages and shows:
Oren Eini's has 3 books at home
Oren Eini's has 2 books queued for reading
Oren Eini's has 7 book recommendations
Oren Eini's has 3 books at home
Oren Eini's has 2 books queued for reading
Oren Eini's has 7 book recommendations
Oren Eini's has 3 books at home
Oren Eini's has 2 books queued for reading
Oren Eini's has 7 book recommendations
Oren Eini's has 3 books at home
Oren Eini's has 2 books queued for reading
Oren Eini's has 7 book recommendations
Oren Eini's has 3 books at home
Oren Eini's has 2 books queued for reading
Oren Eini's has 7 book recommendations

looks like the client tries 5 times but doesn't get a reply.

Note: I've ported the solution to VS 2010 and running under win 7.

I've verified that the client's consume is never reached.

How to debug and fix this?

Thanks,
Ron

Reply to this email directly or view it on GitHub:
#3

[Dizzitune]

Hi ronsher, have you found a solution to this yet? I have the exact same problem using VS2008. Gets 5 MSDTC aborted transactions every time.
However the client consumer is newer created. Set a breakpoint in the MyBooksResponseConsumer constructor and it will never be hit. Therefore I'm guessing that it could be something with the Windsor DI (Im not very used to this framework). Seems like the Consumers never gets registered. This the original registration-code:

container.Kernel.AddFacility("factory", new FactorySupportFacility());

  container.Register(
    Component.For<ISessionFactory>()
      .Instance(sessionFactory),
    Component.For<IMessageModule>()
      .ImplementedBy<NHibernateMessageModule>(),
    Component.For<ISession>()
      .UsingFactoryMethod(() => NHibernateMessageModule.CurrentSession)
      .LifeStyle.Is(LifestyleType.Transient));

[VasoBolkvadze]

i have same issue, did you resolved it ?

[jonathankarsh]

Hi,

Using a debugger attached to the backend library while it's executing the requests, we can see that the SubscriptionDetailsRequestConsumer chokes and dies because the subscription query returns null. That's because the database states that the subscription dates are 2009-01-01 to 2011-01-01. If you make dbo.Subscription's End a future date (there's only one row there), the query succeeds and you get back a response as expected.

It's a demo project which is why not much attention was probably paid to error handling etc.

I'm still seeing some problems (e.g. search falls over, changes you make in the client are not persisted), but the UI actually loads up the query results successfully.

Cheers,
JK