Previously I followed the same link you pasted here.
I had problems in building in eclipse , then I started building with ant
task, which was a success.
But deploying is giving me the explained problem in this thread.

Would appreciate further hepl


2011/5/3 Alexei Fedotov <[email protected]>

> I would suggest following the first instruction from
> http://code.google.com/p/openmeetings/wiki/BuildSourceNew
>
> That's the simplest way.
>
> --
> With best regards / с наилучшими пожеланиями,
> Alexei Fedotov / Алексей Федотов,
> http://dataved.ru/
> +7 916 562 8095
>
>
>
>
> On Tue, May 3, 2011 at 6:48 PM, ambairish kumar
> <[email protected]> wrote:
> > Any time i hit http://localhost:8080/openmeetings/ at my browser..
> > I see the following log at my tomcat console         and  at browser I
> see a
> > blank page.
> > It doesn't show me any errors either in tomcat console or in browser.....
> >
> > Any guidance???
> >
> >
> >
> >
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.jdbc.ConnectionManager -
> > aggressively releasing JDBC connection
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.impl.SessionImpl - opened
> > session at timestamp: 13044338641
> > [DEBUG] ["http-bio-8080"-exec-7]
> org.hibernate.transaction.JDBCTransaction -
> > begin
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.jdbc.ConnectionManager -
> > opening JDBC connection
> > [DEBUG] ["http-bio-8080"-exec-7]
> org.hibernate.transaction.JDBCTransaction -
> > current autocommit status: false
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.jdbc.AbstractBatcher -
> about
> > to open PreparedStatement (open PreparedStatements: 0, globally: 0)
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.SQL -
> >     select
> >         configurat0_.configuration_id as configur1_2_,
> >         configurat0_.comment_field as comment2_2_,
> >         configurat0_.conf_key as conf3_2_,
> >         configurat0_.conf_value as conf4_2_,
> >         configurat0_.starttime as starttime2_,
> >         configurat0_.updatetime as updatetime2_,
> >         configurat0_.deleted as deleted2_,
> >         configurat0_.user_id as user8_2_
> >     from
> >         configuration configurat0_
> >     where
> >         configurat0_.conf_key=?
> >         and configurat0_.deleted=?
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.jdbc.AbstractBatcher -
> about
> > to open ResultSet (open ResultSets: 0, globally: 0)
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.loader.Loader - result
> row:
> > EntityKey[org.openmeetings.app.hibernate.beans.basic.Configuration#12]
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.jdbc.AbstractBatcher -
> about
> > to close ResultSet (open ResultSets: 1, globally: 1)
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.jdbc.AbstractBatcher -
> about
> > to close PreparedStatement (open PreparedStatements: 1, globally: 1)
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.engine.TwoPhaseLoad -
> > resolving associations for
> > [org.openmeetings.app.hibernate.beans.basic.Configuration#12]
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.engine.TwoPhaseLoad - done
> > materializing entity
> > [org.openmeetings.app.hibernate.beans.basic.Configuration#12]
> > [DEBUG] ["http-bio-8080"-exec-7]
> > org.hibernate.engine.StatefulPersistenceContext - initializing non-lazy
> > collections
> > [DEBUG] ["http-bio-8080"-exec-7]
> org.hibernate.transaction.JDBCTransaction -
> > commit
> > [DEBUG] ["http-bio-8080"-exec-7]
> > org.hibernate.event.def.AbstractFlushingEventListener - processing
> > flush-time cascades
> > [DEBUG] ["http-bio-8080"-exec-7]
> > org.hibernate.event.def.AbstractFlushingEventListener - dirty checking
> > collections
> > [DEBUG] ["http-bio-8080"-exec-7]
> > org.hibernate.event.def.AbstractFlushingEventListener - Flushed: 0
> > insertions, 0 updates, 0 deletions to 1 objects
> > [DEBUG] ["http-bio-8080"-exec-7]
> > org.hibernate.event.def.AbstractFlushingEventListener - Flushed: 0
> > (re)creations, 0 updates, 0 removals to 0 collections
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.pretty.Printer - listing
> > entities:
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.pretty.Printer -
> > org.openmeetings.app.hibernate.beans.basic.Configuration{conf_key=
> application.name,
> > starttime
> > 1:09:01.0, updatetime=null, conf_value=OpenMeetings, user_id=null,
> > configuration_id=12, comment=Name of the Browser Title window,
> > deleted=false}
> > [DEBUG] ["http-bio-8080"-exec-7]
> org.hibernate.transaction.JDBCTransaction -
> > committed JDBC Connection
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.jdbc.ConnectionManager -
> > aggressively releasing JDBC connection
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.jdbc.ConnectionManager -
> > releasing JDBC connection [ (open PreparedStatements: 0, globally: 0)
> (open
> > ResultSet
> > y: 0)]
> > [DEBUG] ["http-bio-8080"-exec-7]
> > org.hibernate.event.def.AbstractFlushingEventListener - processing
> > flush-time cascades
> > [DEBUG] ["http-bio-8080"-exec-7]
> > org.hibernate.event.def.AbstractFlushingEventListener - dirty checking
> > collections
> > [DEBUG] ["http-bio-8080"-exec-7]
> > org.hibernate.event.def.AbstractFlushingEventListener - Flushed: 0
> > insertions, 0 updates, 0 deletions to 1 objects
> > [DEBUG] ["http-bio-8080"-exec-7]
> > org.hibernate.event.def.AbstractFlushingEventListener - Flushed: 0
> > (re)creations, 0 updates, 0 removals to 0 collections
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.pretty.Printer - listing
> > entities:
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.pretty.Printer -
> > org.openmeetings.app.hibernate.beans.basic.Configuration{conf_key=
> application.name,
> > starttime
> > 1:09:01.0, updatetime=null, conf_value=OpenMeetings, user_id=null,
> > configuration_id=12, comment=Name of the Browser Title window,
> > deleted=false}
> > [DEBUG] ["http-bio-8080"-exec-7] org.hibernate.jdbc.ConnectionManager -
> > aggressively releasing JDBC connection
> >
> >
> >
> >
> > On 3 May 2011 20:03, ambarish_openmeetings <[email protected]>
> > wrote:
> >>
> >> Hi friends..
> >>
> >> I am building and deploying openmeetings for the first time. I have
> >> furnished what i did.
> >> Someone please verify and guide..
> >>
> >> 1. Taken latest code from SVN server.
> >> 2. Build the code with ant tasks, and the build is a success.
> >> 3. Imported that code in to eclipse and created a war file out of it
> >> (export as war file).
> >> 4. A war file named ROOT.war is created.
> >> 5. renamed that ROOT.war to openmeetings.war and placed in tomcat/
> >> webapps directory and started the tomcat.
> >> 6. when i run http://localhost:8080/openmeetings/   at my browser. I
> >> see a blank page  and at tomcat console it is still at
> >>
> >> 1:09:01.0, updatetime=null, conf_value=OpenMeetings, user_id=null,
> >> configuration_id=12, comment=Name of the Browser Title window,
> >> deleted=false}
> >> [DEBUG] ["http-bio-8080"-exec-4] org.hibernate.jdbc.ConnectionManager
> >> - aggressively releasing JDBC connection
> >>
> >>
> >> Please let me know did i miss any thing..
> >
> >
> >
> > --
> > Ambarish Kumar Lowsarwar
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected].
> > For more options, visit this group at
> > http://groups.google.com/group/openmeetings-user?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>
>


-- 
Ambarish Kumar Lowsarwar

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

Reply via email to