dev@glassfish.java.net

Re: [Fwd: Re: [Issue 2106] <BT6515304>[BLOCKING] SPECJ-like test with EJB3.0 Persistence: Deadlock detected while waiting for resource]

From: Scott Oaks <Scott.Oaks_at_Sun.COM>
Date: Thu, 25 Jan 2007 14:59:54 -0500

Hi Andrei --

I've never seen that error. I poked around Google, if you're using IE,
one suggestion is to change the Internet Options (Connections-LAN
Settings) and uncheck Automatic configuration. And/or to try 127.0.0.1
instead of localhost.

I've copied the glassfish development alias in case anyone else is more
familiar with this.

-Scott

On Thu, 2007-01-25 at 14:45, Andrei Ilitchev wrote:
> Scott,
>
> I am trying to startup gf, and it seems ok, however I can't access
> http://localhost:4848/ with:
> Server Error
> The following error occurred:
> [code=CANT_CONNECT_LOOPBACK] Cannot connect due to potential loopback
> problems
>
> Here's my gf log:
> C:\cvsworkspace\publish\glassfish\bin>asadmin.bat
> Use "exit" to exit and "help" for online help.
> asadmin> start-domain
> Starting Domain domain1, please wait.
> Log redirected to
> C:\cvsworkspace\publish\glassfish\domains\domain1\logs\server.
> log.
> Redirecting output to
> C:/cvsworkspace/publish/glassfish/domains/domain1/logs/ser
> ver.log
> Domain domain1 is ready to receive client requests. Additional services are
> bein
> g started in background.
> Domain [domain1] is running [Sun Java System Application Server 9.1 (build
> b34)]
> with its configuration and logs at:
> [C:\cvsworkspace\publish\glassfish\domains]
> .
> Admin Console is available at [http://localhost:4848].
> Use the same port [4848] for "asadmin" commands.
> User web applications are available at these URLs:
> [http://localhost:8080 https://localhost:8181 ].
> Following web-contexts are available:
> [/web1 /__wstx-services ].
> Standard JMX Clients (like JConsole) can connect to JMXServiceURL:
> [service:jmx:rmi:///jndi/rmi://ailitche-pc:8686/jmxrmi] for domain
> management pu
> rposes.
> Domain listens on at least following ports for connections:
> [8080 8181 4848 3700 3820 3920 8686 ].
> Domain does not support application server clusters and other standalone
> instanc
> es.
>
> asadmin>
>
> Could you please advice what am I doing wrong here.
>
> Tahnks,
>
> Andrei
> ----- Original Message -----
> From: "Scott Oaks" <Scott.Oaks_at_Sun.COM>
> To: "Andrei Ilitchev" <andrei.ilitchev_at_oracle.com>
> Cc: <Meenatchi.Palani_at_Sun.COM>
> Sent: Tuesday, January 23, 2007 1:44 PM
> Subject: Re: [Fwd: Re: [Issue 2106] <BT6515304>[BLOCKING] SPECJ-like test
> with EJB3.0 Persistence: Deadlock detected while waiting for resource]
>
>
> >
> >> 1. how to deploy and run the ear file;
> >
> > Build the ear file with ant (ant ear)
> > Deploy jars/test.ear by copying it to
> > /path_to_appserver/domains/domain1/autodeploy
> > (or whatever domain you are using).
> > Visit the URL listed in the README
> >
> >> 2. how to define a data source;
> >
> > After you start the app server, load http://host:4848/ in your browser
> > (assuming you selected the standard ports when you installed). Log in.
> >
> > [Note that on the login page, you can deploy the ear too.]
> >
> > In the left pane, expand resources. Click on connectionpools. Click new;
> > give it any name you want, resource type javax.sql.DataSource, database
> > vendor Oracle. Click next. Fill in any properties you want to change (in
> > particular, fill in the user, password, and URL). Click finish.
> >
> > Go back to the leftpane and click jdbc resources. Define a resource
> > named jdbc/TestDB (or whatever is specified in your persistence.xml) and
> > assign it the appropriate pool.
> >
> >> 3. where to stick the Oracle jdbc driver to be used by the data source
> >> (I'd like to use my Oracle db).
> >
> > /path_to_appserver/domains/domain1/lib/ext.
> >
> > -Scott
> >
> >>
> >> Thanks,
> >>
> >> Andrei
> >> ----- Original Message -----
> >> From: Meena Palani
> >> To: andrei.ilitchev_at_oracle.com
> >> Cc: Scott.Oaks_at_Sun.COM
> >> Sent: Tuesday, January 23, 2007 12:17 PM
> >> Subject: Re: [Fwd: Re: [Issue 2106] <BT6515304>[BLOCKING]
> >> SPECJ-like test with EJB3.0 Persistence: Deadlock detected
> >> while waiting for resource]
> >>
> >> Hi Andrei,
> >>
> >> If you can do this test, I think it will be more efficient so
> >> we don't have to go back and forth between us.
> >> What I can do is maybe initially setup these requirements on
> >> my setup and give you my setup for debugging. You can try with
> >> all the workarounds/fixes going forward. Let me know if this
> >> is ok.
> >>
> >> Scott Oaks wrote On 01/23/07 09:12,:
> >> > Hi Meena --
> >> >
> >> > There are instructions in the README and README.schema with the
> >> test.
> >> >
> >> > Basically, you need to create the appropriate database schema
> >> (but
> >> > actually, you have the SPECj database and can test against
> >> that), create
> >> > a JNDI resource jdbc/TestDB in the appserver to point to that
> >> database,
> >> > build the ear file, deploy it to the appserver, and visit
> >> > http://host:port/test/TestServlet twice -- the second time will
> >> hang.
> >> >
> >> > The persistence.xml file he's asking you to add the logging
> >> levels to is
> >> > in the meta directory -- you can change that file, re-build the
> >> test,
> >> > and redeploy.
> >> >
> >> > Andrei -- did you have problems running the test?
> >> >
> >> > -Scott
> >> >
> >> > On Tue, 2007-01-23 at 12:05, Meena Palani wrote:
> >> >
> >> > > Hi Scott,
> >> > >
> >> > > Andrei is asking me to run the simple test you had tried out.
> >> Can you
> >> > > let me know how to test it ?
> >> > >
> >> > > -------- Original Message --------
> >> > > Subject:
> >> > > Re: [Issue 2106] [BLOCKING]
> >> > > SPECJ-like test with EJB3.0
> >> > > Persistence: Deadlock detected
> >> > > while waiting for resource
> >> > > Date:
> >> > > Tue, 23 Jan 2007 09:34:02 -0500
> >> > > From:
> >> > > Andrei Ilitchev
> >> > > <andrei.ilitchev_at_oracle.com>
> >> > > To:
> >> > > Meenatchi.Palani_at_Sun.COM
> >> > > CC:
> >> > > Deepa Singh <Deepa.Singh_at_Sun.COM>
> >> > > References:
> >> > > <00b901c73e57$ac976bb0$4c349c0a_at_ca.oracle.com>
> >> <45B51AB3.8090304_at_sun.com> <45B5403E.2020107_at_Sun.COM>
> >> > >
> >> > > Hi Meenatchi,
> >> > >
> >> > > Yes, I was hoping for the simple test.
> >> > >
> >> > > Thanks,
> >> > >
> >> > > Andrei
> >> > > ----- Original Message -----
> >> > > From: Meena Palani
> >> > > To: Andrei Ilitchev
> >> > > Cc: Deepa Singh
> >> > > Sent: Monday, January 22, 2007 5:52 PM
> >> > > Subject: Re: [Issue 2106] <BT6515304>[BLOCKING]
> >> SPECJ-like
> >> > > test with EJB3.0 Persistence: Deadlock detected while
> >> waiting
> >> > > for resource
> >> > >
> >> > > Hi Andrei,
> >> > >
> >> > > Are you asking to do this on the actual specj
> >> benchmark test
> >> > > or the simple test that was attached in the bug
> >> report? That
> >> > > simple test was created by Scott Oaks from
> >> performance team. I
> >> > > use the actual specj benchmark for our testing
> >> purpose.
> >> > >
> >> > >
> >> > > Deepa Singh wrote On 01/22/07 12:12,:
> >> > > > Hi Andrei,
> >> > > > Meenatchi is owner of this test. I have forwarded
> >> your
> >> > > > request to her.
> >> > > >
> >> > > > Meenatchi, can you please re-run your test with
> >> increased
> >> > > > logging level? You can update mirrored issue 2106
> >> directly
> >> > > > so that Andrei can also see.
> >> > > >
> >> > > > Andrei Ilitchev said the following on 1/22/2007
> >> 11:01 AM:
> >> > > > > Could you please run the test with debug logging
> >> enabled
> >> > > > > and send me the log.
> >> > > > > In persistence.xml add toplink.logging.level
> >> property:
> >> > > > > <properties>
> >> > > > > <property name="toplink.bind-all-parameters"
> >> > > > > value="true"/>
> >> > > > > <property name="toplink.logging.level"
> >> > > > > value="FINEST"/>
> >> > > > > </properties>
> >> > > > >
> >> > > > > Thanks,
> >> > > > >
> >> > > > > Andrei
> >> > > > > ----- Original Message ----- From: "Andrei
> >> Ilitchev"
> >> > > > > <andrei.ilitchev_at_oracle.com>
> >> > > > > To: "Deepa Singh" <Deepa.Singh_at_sun.com>
> >> > > > > Sent: Monday, January 22, 2007 1:54 PM
> >> > > > > Subject: Re: [Issue 2106] <BT6515304>[BLOCKING]
> >> SPECJ-like
> >> > > > > test with EJB3.0 Persistence: Deadlock detected
> >> while
> >> > > > > waiting for resource
> >> > > > >
> >> > > > >
> >> > > > > > Thanks, I've got it.
> >> > > > > > ----- Original Message ----- From: "Deepa
> >> Singh"
> >> > > > > > <Deepa.Singh_at_sun.com>
> >> > > > > > To: <ailitche_at_dev.java.net>
> >> > > > > > Sent: Monday, January 22, 2007 1:47 PM
> >> > > > > > Subject: Re: [Issue 2106] <BT6515304>[BLOCKING]
> >> > > > > > SPECJ-like test with EJB3.0 Persistence:
> >> Deadlock
> >> > > > > > detected while waiting for resource
> >> > > > > >
> >> > > > > >
> >> > > > > > > Can you please re-try?
> >> > > > > > > Otherwise, I have attached testcase to this
> >> email as
> >> > > > > > > well.
> >> > > > > > >
> >> > > > > > > ailitche_at_dev.java.net said the following on
> >> 1/22/2007
> >> > > > > > > 9:56 AM:
> >> > > > > > > >
> >> https://glassfish.dev.java.net/issues/show_bug.cgi?id=2106
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > ------- Additional comments from
> >> > > > > > > > ailitche_at_dev.java.net Mon Jan 22 17:56:01
> >> +0000 2007
> >> > > > > > > > -------
> >> > > > > > > > I couldn't download the test case. Could
> >> you please
> >> > > > > > > > repost.
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > > --
> >> > > > > > > Sun Java Enterprise System-Quality
> >> > > > > > > USCA14-304
> >> > > > > > > 4140 Network Circle
> >> > > > > > > Santa Clara,95054
> >> > > > > > > x17289
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >
> >
>