You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Vasily Zakharov (JIRA)" <de...@geronimo.apache.org> on 2006/04/03 21:40:44 UTC
[jira] Created: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
SPECjAppServer2004 Deployment Descriptors
-----------------------------------------
Key: GERONIMO-1800
URL: http://issues.apache.org/jira/browse/GERONIMO-1800
Project: Geronimo
Type: Task
Security: public (Regular issues)
Reporter: Vasily Zakharov
Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Vasily Zakharov (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=all ]
Vasily Zakharov updated GERONIMO-1800:
--------------------------------------
Attachment: specjms.xml
JMS connector DD
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=all ]
Jacek Laskowski resolved GERONIMO-1800:
---------------------------------------
Fix Version: 1.x
Resolution: Invalid
SPECjAppServ2004 is a commercial application, so we can't ship it. The plans will be available in our documentation, though. We can't do much about it other than writing a doc and attach the plans to it.
Thanks for the work you've done, Vasily! It's greatly appreciated.
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Fix For: 1.x
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=all ]
Jacek Laskowski closed GERONIMO-1800:
-------------------------------------
No need to keep the issue open. Please use the user mailing list. Don't forget to help us with documenting it, Vasily ;) Thanks!
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Fix For: 1.x
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Vasily Zakharov (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=all ]
Vasily Zakharov updated GERONIMO-1800:
--------------------------------------
Attachment: specj2004-deployment-plan.xml
SPECjAppServer2004 application DD
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=comments#action_12373767 ]
Jacek Laskowski commented on GERONIMO-1800:
-------------------------------------------
You don't need to wait for anybody, but go straight to the page and write the doc. It's the only way to have anything available for the commercial app.
Would be great if we could convince them to include the plans in their distro. Wish you luck!
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Vasily Zakharov (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=comments#action_12373765 ]
Vasily Zakharov commented on GERONIMO-1800:
-------------------------------------------
Good idea, I can write the doc. Should I put the doc here for someone to put it to the site you mentioned?
I don't think the plans should be in application (i. e. in .cars), as it would require correcting the application's build system which is an extra effort for the end-user.
The application (http://www.spec.org/jAppServer2004/) is commercial and is not freely available.
When we manage to run SPECjAppServer2004 on Geronimo successfuly, we could send our plans to SPEC for them to include those plans in future benchmark release.
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Vasily Zakharov (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=comments#action_12374188 ]
Vasily Zakharov commented on GERONIMO-1800:
-------------------------------------------
The investigations show that the cause for the stack above is the following exception. The reason for this exception is unclear for now.
javax.ejb.EJBException: javax.ejb.FinderException: Error executing statement: SELECT C.C_ID FROM C_CUSTOMER C WHERE C.C_ID = ?
at org.spec.jappserver.corp.customerses.ejb.CustomerSesEJB.checkCustomerCredit(CustomerSesEJB.java:246)
at org.spec.jappserver.corp.customerses.ejb.CustomerSesEJB$$FastClassByCGLIB$$c445ce6f.invoke(<generated>)
at org.openejb.dispatch.AbstractMethodOperation.invoke(AbstractMethodOperation.java:90)
at org.openejb.slsb.BusinessMethod.execute(BusinessMethod.java:67)
at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72)
at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56)
at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81)
at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:119)
at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80)
at org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:98)
at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:142)
at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80)
at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82)
at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238)
at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129)
at org.openejb.proxy.SessionEJBObject$$EnhancerByCGLIB$$52a1c83e.checkCustomerCredit(<generated>)
at org.spec.jappserver.servlet.helper.SpecAction.atomicityTestTwo(SpecAction.java:166)
at org.spec.jappserver.servlet.helper.SpecServletAction.doAtomicityTests(SpecServletAction.java:1304)
at org.spec.jappserver.servlet.SpecAppServlet.performTask(SpecAppServlet.java:166)
at org.spec.jappserver.servlet.SpecAppServlet.doGet(SpecAppServlet.java:96)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:99)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
at org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: javax.ejb.FinderException: Error executing statement: SELECT C.C_ID FROM C_CUSTOMER C WHERE C.C_ID = ?
at org.openejb.entity.cmp.SingleValuedFinder.execute(SingleValuedFinder.java:83)
at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72)
at org.apache.geronimo.naming.java.ComponentContextInterceptor.invoke(ComponentContextInterceptor.java:56)
at org.openejb.ConnectionTrackingInterceptor.invoke(ConnectionTrackingInterceptor.java:81)
at org.openejb.entity.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:136)
at org.openejb.entity.cmp.InTxCacheInterceptor.invoke(InTxCacheInterceptor.java:90)
at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:119)
at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80)
at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82)
at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238)
at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129)
at org.openejb.proxy.EntityEJBLocalHome$$EnhancerByCGLIB$$2e548314.findByPrimaryKey(<generated>)
at org.spec.jappserver.corp.customerses.ejb.CustomerSesEJB.checkCustomerCredit(CustomerSesEJB.java:243)
... 38 more
Caused by: org.tranql.ql.QueryException: Error executing statement: SELECT C.C_ID FROM C_CUSTOMER C WHERE C.C_ID = ?
at org.tranql.sql.jdbc.JDBCQueryCommand.execute(JDBCQueryCommand.java:79)
at org.tranql.cache.cache.FindByPKCacheQueryCommand.execute(FindByPKCacheQueryCommand.java:66)
at org.openejb.entity.cmp.CMPFinder.execute(CMPFinder.java:99)
at org.openejb.entity.cmp.SingleValuedFinder.execute(SingleValuedFinder.java:80)
... 50 more
Caused by: SQL Exception: Schema 'MYAPP' does not exist
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(Unknown Source)
at org.apache.derby.jdbc.Driver30.newEmbedPreparedStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source)
at org.apache.derby.iapi.jdbc.BrokeredConnection.prepareStatement(Unknown Source)
at org.tranql.connector.jdbc.ConnectionHandle.prepareStatement(ConnectionHandle.java:231)
at org.tranql.sql.jdbc.JDBCQueryCommand.execute(JDBCQueryCommand.java:62)
... 53 more
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Fix For: 1.x
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Vasily Zakharov (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=comments#action_12373800 ]
Vasily Zakharov commented on GERONIMO-1800:
-------------------------------------------
The deployment string for Derby connector turned out (thanks to David Jencks) to be wrong - XA connector should be used instead. Here's the corrected line:
java -jar bin/deployer.jar --user system --password manager deploy repository/tranql/rars/tranql-connector-derby-embed-xa-1.1.rar specdb.xml
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Fix For: 1.x
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Vasily Zakharov (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=all ]
Vasily Zakharov updated GERONIMO-1800:
--------------------------------------
Attachment: specdb.xml
Derby database connector DD
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Attachments: specdb.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Vasily Zakharov (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=comments#action_12373763 ]
Vasily Zakharov commented on GERONIMO-1800:
-------------------------------------------
The deployment strings are:
java -jar bin/deployer.jar --user system --password manager deploy repository/tranql/rars/tranql-connector-derby-embed-local-1.1.rar specdb.xml
java -jar bin/deployer.jar --user system --password manager deploy repository/activemq/rars/activemq-ra-3.2.1.rar specjms.xml
java -jar bin/deployer.jar --user system --password manager deploy SPECjAppServer.ear specj2004-deployment-plan.xml
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=comments#action_12373764 ]
Jacek Laskowski commented on GERONIMO-1800:
-------------------------------------------
I think the patch should be accompanied with a doco on http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Sample+applications as 'SPECjAppServ2004'. I wonder where the plans should go. Should they be in applications? How can I get the ear? Is it freely available? The best choice would be to create cars and let people download it, but it requires the app be open to public (which I think is not). If it's not, I think the only choice is to describe the process of deploying the app on the aforementioned page and attach the files there.
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1800) SPECjAppServer2004 Deployment
Descriptors
Posted by "Vasily Zakharov (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1800?page=comments#action_12374187 ]
Vasily Zakharov commented on GERONIMO-1800:
-------------------------------------------
Here's the stack trace that now appears in the log when trying to run the SPECjAppServ2004 atomicity tests:
javax.transaction.TransactionRolledbackException: javax.ejb.FinderException: Error executing statement: SELECT C.C_ID FROM C_CUSTOMER C WHERE C.C_ID = ?
at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:126)
at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80)
at org.openejb.slsb.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:98)
at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:140)
at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80)
at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82)
at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:238)
at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:129)
at org.openejb.proxy.SessionEJBObject$$EnhancerByCGLIB$$4084bef.checkCustomerCredit(<generated>)
at org.spec.jappserver.servlet.helper.SpecAction.atomicityTestTwo(SpecAction.java:166)
at org.spec.jappserver.servlet.helper.SpecServletAction.doAtomicityTests(SpecServletAction.java:1304)
at org.spec.jappserver.servlet.SpecAppServlet.performTask(SpecAppServlet.java:166)
at org.spec.jappserver.servlet.SpecAppServlet.doGet(SpecAppServlet.java:96)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:99)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
at org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
> SPECjAppServer2004 Deployment Descriptors
> -----------------------------------------
>
> Key: GERONIMO-1800
> URL: http://issues.apache.org/jira/browse/GERONIMO-1800
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Reporter: Vasily Zakharov
> Fix For: 1.x
> Attachments: specdb.xml, specj2004-deployment-plan.xml, specjms.xml
>
> Here're the deployment descriptors I'm trying to use to deploy the SPECjAppServer2004 benchmark.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira