JDBC In Petstore
Does any body know what the last part of this if means in the
GenericCatalogDAO class in the petstore application.
if (start >= 0 && resultSet.absolute(start + 1)) {
I have a result set (four rows), start is 0 so the first part of the if is true,but i do not seem to get into this if block.
This problem occurs when going from the main petstore screen to the category screen, gets there but the getproducts method does not populate the category.jsp by returning the Page of results. This is done inside this if, in the getproducts method of this class.
Tried removing the second part of the if (to experiment) and get a catalog exception below.
com.sun.j2ee.blueprints.catalog.client.CatalogException: SQLException: Exhausted Resultset
Can Anybody help?
Cheers,
Roger
Hi,
Here's some documentation on what ResultSet.absolute does:
http://javaalmanac.com/egs/java.sql/MoveCursor.html
Here's the JavaDoc details:
http://java.sun.com/j2se/1.5.0/docs/api/java/sql/ResultSet.html#absolute(int)
Please let me know if you still have questions.
-Larry
Similar Messages
-
Problems starting up PetStore demo with W6.1 on Solaris
I just finished installing W6.1 on Solaris and I tried to run the PetStorr demo
but I keep getting the following exception. Unfortunately, this error message
does not tell anything because there is no indication as to what the hell is wrong.
If this stack trace looks familar to anyone, please let me know how you solved
your problems.
The only change I made the petstore config.xml file was I changed the HTTP listening
port to 9001. Here is my pool configuration...
<JDBCConnectionPool CapacityIncrement="1"
DriverName="COM.cloudscape.core.JDBCDriver" InitialCapacity="1"
MaxCapacity="1" Name="petstorePool"
Properties="user=none;password=none;server=none"
Targets="petstoreServer" TestConnectionsOnReserve="true"
TestTableName="product" URL="jdbc:cloudscape:petStore"/>
----------------Here is the stack trace-----------------------
####<Feb 1, 2002 2:06:39 PM EST> <Error> <JDBC> <jordan> <petstoreServer> <main>
<system> <> <001060> <Cannot startup connection pool "petstorePool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
SQL Exception: Failed to start database 'petStore', see the next exception for
details.
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.t(Unknown Source)
at c8e.k.q.l(Unknown Source)
at c8e.k.q.<init>(Unknown Source)
at c8e._b.e.<init>(Unknown Source)
at c8e._b.c.getNewLocalConnection(Unknown Source)
at c8e.k.v.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy32.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy32.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)Thanks for the reply. I checked the scripts and we have all proper CLASSPATH and
environment settings as you have indicated. But you made me realize one thing
that I did not check before. There is a database log file in ./samples/eval/cloudscape/data/
which I checked and found that the database was attempting to write to a file
in which it did not have the proper permission to access. I'm hoping that this
is the root of my problem.
thanks again,
SAF
"pavans" <[email protected]> wrote:
Hey..
One of our team member was getting this same problem...
I think it is something to do with cloudscape setup..
try this out..
Are you able to start cloudscape by java COM.cloudscape.tools.view cmd?
make sure you have ".\samples\eval\cloudscape\lib\cloudscape.jar" in
classpath of startpetstore.cmd file
-Dcloudscape.system.home=./samples/eval/cloudscape/data in
startPetStore.cmd
If I remember correctly, we changed some settings like above ...and error
was gone
I guess you have table "product" in your "demo" database.
"SAF" <[email protected]> wrote in message
news:[email protected]...
I just finished installing W6.1 on Solaris and I tried to run the PetStorrdemo
but I keep getting the following exception. Unfortunately, this errormessage
does not tell anything because there is no indication as to what thehell
is wrong.
If this stack trace looks familar to anyone, please let me know howyou
solved
your problems.
The only change I made the petstore config.xml file was I changed theHTTP
listening
port to 9001. Here is my pool configuration...
<JDBCConnectionPool CapacityIncrement="1"
DriverName="COM.cloudscape.core.JDBCDriver" InitialCapacity="1"
MaxCapacity="1" Name="petstorePool"
Properties="user=none;password=none;server=none"
Targets="petstoreServer" TestConnectionsOnReserve="true"
TestTableName="product" URL="jdbc:cloudscape:petStore"/>
----------------Here is the stack trace-----------------------
####<Feb 1, 2002 2:06:39 PM EST> <Error> <JDBC> <jordan> <petstoreServer><main>
<system> <> <001060> <Cannot startup connection pool "petstorePool"weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
SQL Exception: Failed to start database 'petStore', see the next exceptionfor
details.
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.t(Unknown Source)
at c8e.k.q.l(Unknown Source)
at c8e.k.q.<init>(Unknown Source)
at c8e._b.e.<init>(Unknown Source)
at c8e._b.c.getNewLocalConnection(Unknown Source)
at c8e.k.v.connect(Unknown Source)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connection
EnvFactory.java:193)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connection
EnvFactory.java:134)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
..java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy32.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
..java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connection
EnvFactory.java:209)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connection
EnvFactory.java:134)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
..java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy32.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
..java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35) -
Petstore 1.3.1 NAMED_SEQUENCE problem: "The transaction is no longer active"
Hi all,
I am currently trying to get Petstore 1.3.1 going on WLS 7.0.0.1 an got
into quite som trouble (btw, does anyone have expereince with this
cofiguration?). After successful deployment in /application I tried the
"populate database" link on ~/petstore/index.jsp and got:
java.sql.SQLException: The transaction is no longer active (status = Committed). No further JDBC access is allowed within this transaction.
at weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:541)
at weblogic.jdbc.jts.ResultSet.close(ResultSet.java:293)
at weblogic.jdbc.rmi.internal.ResultSetImpl.close(ResultSetImpl.java:144)
at weblogic.jdbc.rmi.SerialResultSet.close(SerialResultSet.java:96)
at weblogic.jdbc.rmi.SerialResultSet.close(SerialResultSet.java:87)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.releaseResultSet(RDBMSPersistenceManager.java:1797)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.releaseResources(RDBMSPersistenceManager.java:1679)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.execGenKeyNamedSequenceTableUpdateAndQuery(RDBMSPersistenceManager.java:1489)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getNextGenKeyNamedSequenceTable(RDBMSPersistenceManager.java:1307)
at com.sun.j2ee.blueprints.address.ejb.AddressEJB_fvu9sn__WebLogic_CMP_RDBMS.ejbCreate(AddressEJB_fvu9sn__WebLogic_CMP_RDBMS.java:1723)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.DBManager.create(DBManager.java:737)
at weblogic.ejb20.manager.DBManager.localCreate(DBManager.java:716)
at weblogic.ejb20.internal.EntityEJBLocalHome.create(EntityEJBLocalHome.java:182)
at com.sun.j2ee.blueprints.address.ejb.AddressEJB_fvu9sn_LocalHomeImpl.create(AddressEJB_fvu9sn_LocalHomeImpl.java:155)
at com.sun.j2ee.blueprints.petstore.tools.populate.AddressPopulator.createAddress(AddressPopulator.java:94) at com.sun.j2ee.blueprints.petstore.tools.populate.AddressPopulator.access$7(AddressPopulator.java)
at com.sun.j2ee.blueprints.petstore.tools.populate.AddressPopulator$1.create(AddressPopulator.java:73)
at com.sun.j2ee.blueprints.petstore.tools.populate.XMLDBHandler.endElement(XMLDBHandler.java:145)
at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:595)
at com.sun.j2ee.blueprints.petstore.tools.populate.XMLDBHandler.endElement(XMLDBHandler.java:158)
at weblogic.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1411)
at weblogic.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator.java:1613)
at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1219)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:396)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1119)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:133)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at com.sun.j2ee.blueprints.petstore.tools.populate.PopulateServlet.populate(PopulateServlet.java:162)
at com.sun.j2ee.blueprints.petstore.tools.populate.PopulateServlet.doPost(PopulateServlet.java:118)
at com.sun.j2ee.blueprints.petstore.tools.populate.PopulateServlet.doGet(PopulateServlet.java:106)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:945)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:332)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:20)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.sun.j2ee.blueprints.signon.web.SignOnFilter.doFilter(SignOnFilter.java:151)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.sun.j2ee.blueprints.encodingfilter.web.EncodingFilter.doFilter(EncodingFilter.java:77)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5366)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3043)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2468)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
and similar traces for ContactInfo, CreditCard, Account, Profile, ...
I nevertheless get to the main screen of the Petstore as if everything
worked well. In fact, it seems like the DB got populated somewhat
correctly; only tbe named sequence tables are unchanged (btw: are the
named sequences expected to be auto-created with
create-default-dbms-tables enabled ?). The strange thing is that every
correct row (in my case having the even IDs) is followd by an all (except the
odd numbered ID field) "NULL" row. This does not happen in all
...EJBTABLEs --- Address and ContactInfo for example are affected, but Profile
is not.
It seems as if ordering a rattlesnake would work well, even though more
of the same type of Execptions appear in the jdbc log. I suspect that the
trouble will start when the 10 cached ID are exhausted.
Any ideas?
KaiI just tried the Petstore 1.3 example provided with WLS 7.0.0.1 and found
petty much the same exception after enabling the jdbc log:
java.sql.SQLException: The transaction is no longer active (status = Committed). No further JDBC access is allowed within this transaction.
at weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:541)
at weblogic.jdbc.jts.ResultSet.close(ResultSet.java:293)
at weblogic.jdbc.rmi.internal.ResultSetImpl.close(ResultSetImpl.java:144)
at weblogic.jdbc.rmi.SerialResultSet.close(SerialResultSet.java:96)
at weblogic.jdbc.rmi.SerialResultSet.close(SerialResultSet.java:87)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.releaseResultSet(RDBMSPersistenceManager.java:1797)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.releaseResources(RDBMSPersistenceManager.java:1679)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.execGenKeyNamedSequenceTableUpdateAndQuery(RDBMSPersistenceManager.java:1489)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getNextGenKeyNamedSequenceTable(RDBMSPersistenceManager.java:1307)
at com.sun.j2ee.blueprints.po.address.ejb.AddressEJB_fvu9sn__WebLogic_CMP_RDBMS.ejbCreate(AddressEJB_fvu9sn__WebLogic_CMP_RDBMS.java:1755)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.DBManager.create(DBManager.java:737)
at weblogic.ejb20.manager.DBManager.localCreate(DBManager.java:716)
at weblogic.ejb20.internal.EntityEJBLocalHome.create(EntityEJBLocalHome.java:182)
at com.sun.j2ee.blueprints.po.address.ejb.AddressEJB_fvu9sn_LocalHomeImpl.create(AddressEJB_fvu9sn_LocalHomeImpl.java:86)
at com.sun.j2ee.blueprints.po.purchaseorder.ejb.PurchaseOrderHelper.persistPoCMRInfo(PurchaseOrderHelper.java:116)
at com.sun.j2ee.blueprints.po.purchaseorder.ejb.PurchaseOrderHelper.persistPO(PurchaseOrderHelper.java:164) at com.sun.j2ee.blueprints.opc.ejb.MsgBean.doWork(MsgBean.java:103)
at com.sun.j2ee.blueprints.opc.ejb.MsgBean.onMessage(MsgBean.java:72)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:348)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:282)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:263)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2309)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2232)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
Is there a problem with my general setup maybe, or is this exception to
be ignored?
Kai -
Petstore 1.3 with Oracle 8.1.7 on Solaris 9 - deployment error
Hello,
I'm trying to get Petstore 1.3 shipped with WebLogic Server 7.0 to work with Oracle
8.1.7 on Solaris 9 with a third-party (Oracle) jdbc driver (classes12). I did
the following:
1) created a new connection pool with the correct Oracle database URL and driver
class name (oracle.jdbc.driver.OracleDriver), also user/password properties for
the Oracle db, and the WL server selected in targets;
2) created a database schema for Oracle based on the data in Pointbase and the
weblogic-cmp-rdbms-jar file as well as petstore_catalog_utf8.sql;
3) created a new tx datasource pointing to the Oracle conn pool;
4) modified the catalog component's ejb-jar.xml file's env-entry to contain CatalogOracleDAOImpl;
5) put weblogic.jar in the classpath;
6) used Java's dbping utility to check connection to the database via the Oracle
driver (works fine--no network adapter error or anything related).
I then rebuilt the ear files (build is successful), but when deploying get the
following error:
"Cannot deploy EJB AccountEJB from customerEjb.jar. Cannot find datasource for
JNDI datasource-petstorePool" and says to make sure the JNDI name and deployment
descriptors are correct (I checked the customer component's deployment descriptors
against the tx datasources' JNDI and they match).
What step(s) am I missing? Any suggestions on what else I need to modify would
be very much appreciated.
Thanks,
Beverly ClaireBeverly:
If you have 8.1, then you should be able to simply and easily create a
connection pool to petstore via the console.
The current error you encountering: "petstorePool does not exist" is
because either:
petstorePool is not defined or there was a failure when the pool was first
created trying to connect to the DBMS.
The full errror should be in the log file prior to the TXDatasource error.
Cheers
mbg
"Beverly Claire" <[email protected]> wrote in message
news:[email protected]...
>
Hello Rob,
Thanks for your reply. Yes, the tx datasource's JNDI name isdatasource-petstorePool.
The server log says that "petstorePool does not exist".
My conn pool contents:
Name: petstorePool
URL: jdbc:oracle:thin:@<replaced with db address>:<replaced with dbport>:<replaced
with db SID>
Driver Class Name: oracle.jdbc.driver.OracleDriver
Properties: user=<replaced with username*>
password=<replaced with password*>
*same username and password used to set up the Petstore tables in Oracledb.
>
My tx datasource contents:
Name: PetstoreDataSource
JNDI: datasource-petstorePool
Pool Name: petstorePool
No, actually we're not evaluating in the sense of just-trying-things-out.One
of our clients is considering an application server. They're relying on usfor
help in choosing which would be best. As of now, we are comparing BEA WLServer
7 and 8.1, Sun ONE Application Server 7 EE, Oracle 9i Application Server,and
Fujitsu Interstage v5 Application Server. For cluster testing andperformance
comparison purposes, we'd like to use the same J2EE Application across allservers,
and the obvious choice is Petstore 1.3. One aim is to smoothly connect toan Oracle
database. The other app servers provide setup scripts and databaseschemas for
Petstore-with-Oracle, so db conn and deployment are not a problem at all.As for
WL, we've been trying to get Petstore (both the version downloaded fromSun's
Java Blueprints and the version that shipped with WL 7) to work withOracle, but
no luck so far. It's getting a bit frustrating, given the ease with whichthings
worked out with the other app servers.
Yes, I've tried out Avitek MedRec for WL 8.1, and this time BEA has kindlymade
provisions for Oracle db, so connection to Oracle is not a problem. I'mhoping
BEA will come around to doing the same thing for Petstore, although I'mguessing
that won't be in the near future.
Any other suggestions would be much appreciated.
Thanks,
Bevery Claire -
Problem in Installing PetStore 1.3
Dears, I am facing problem in installing petstore following is my console's out put.Please advise.
I am following the same instructions provided in the docs.
E:\j2sdkee1.2.1\public_html\petstore1.3>setup
Buildfile: setup.xml
init:
help:
[echo] Before running this script, please start the cloudscape database and J2EE server by running the following commands:
[echo] <change directory to j2sdkee1.3/bin>
[echo] cloudscape -start
[echo] j2ee -verbose
create_jms_queues:
[echo] Creating JMS Queues ....
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
create_users:
[echo] Creating users ....
[java]
[java] Group default has been added successfully.
[java]
[java] User jps_admin has been added successfully.
[java]
[java] User rcvr has been added successfully.
create_supplier_db:
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
create_opc_db:
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
core:
[echo] The J2EE SDK is now successfully configured to run the petstore application. Please restart cloudscape and the j2ee servers, and deploy all the ear files. You can do this by issuing the fo
llowing commands:
[echo] change directory to j2sdkee1.3/bin
[echo] cloudscape -stop
[echo] j2ee -stop
[echo] cloudscape -start
[echo] j2ee -verbose
[echo] change directory to petstore1.3
[echo] setup.bat deploy (or on Unix, setup.sh deploy)
BUILD SUCCESSFUL
Total time: 22 seconds
E:\j2sdkee1.2.1\public_html\petstore1.3>cd ..
E:\j2sdkee1.2.1\public_html>cd ..
E:\j2sdkee1.2.1>cd bin
E:\j2sdkee1.2.1\bin>cloudscape -stop
URL=[jdbc:rmi:jdbc:cloudscape:]
Attempting to shutdown RmiJdbc server
RmiJdbc Server RmiAddr is: //aliawan/RmiJdbcServer
WARNING: Shutdown was successful!
E:\j2sdkee1.2.1\bin>j2ee -stop
Shutting down the J2EE server.
E:\j2sdkee1.2.1\bin>cd ../public_html
E:\j2sdkee1.2.1>cd /public_html
The syntax of the command is incorrect.
E:\j2sdkee1.2.1>cd public_html
E:\j2sdkee1.2.1\public_html>cd petstore
The system cannot find the path specified.
E:\j2sdkee1.2.1\public_html>cd petstore1.3
E:\j2sdkee1.2.1\public_html\petstore1.3>setup.bat deploy
Buildfile: setup.xml
init:
deploy:
[echo] Deploying ears ....
[java]
[java] Sender object Deploytool (Main) : Neither this XML document's public nor system id's could be resolved: java.net.UnknownHostException: java.sun.com java.sun.com
[java] on parsing the doucment corresponding to class com.sun.enterprise.deployment.xml.EjbBundleNode
[java] Java Result: 1
[java]
[java] Sender object Deploytool (Main) : Neither this XML document's public nor system id's could be resolved: java.net.UnknownHostException: java.sun.com java.sun.com
[java] on parsing the doucment corresponding to class com.sun.enterprise.deployment.xml.ApplicationNode
[java] Java Result: 1
[java]
[java] Sender object Deploytool (Main) : Neither this XML document's public nor system id's could be resolved: java.net.UnknownHostException: java.sun.com java.sun.com
[java] on parsing the doucment corresponding to class com.sun.enterprise.deployment.xml.ApplicationNode
[java] Java Result: 1
[java]
[java] Sender object Deploytool (Main) : Neither this XML document's public nor system id's could be resolved: java.net.UnknownHostException: java.sun.com java.sun.com
[java] on parsing the doucment corresponding to class com.sun.enterprise.deployment.xml.ApplicationNode
[java] Java Result: 1
[echo] The petstore application is now installed.
[echo] Please restart your cloudscape database and the J2EE server, and then point your browser to http://localhost:8000/petstore to access petstore.
BUILD SUCCESSFUL
Total time: 17 seconds
E:\j2sdkee1.2.1\public_html\petstore1.3>cd ..
E:\j2sdkee1.2.1\public_html>cd ..
E:\j2sdkee1.2.1>cd bin
E:\j2sdkee1.2.1\bin>cloudscape -stop
URL=[jdbc:rmi:jdbc:cloudscape:]
Attempting to shutdown RmiJdbc server
RmiJdbc Server RmiAddr is: //aliawan/RmiJdbcServer
WARNING: Shutdown was successful!
E:\j2sdkee1.2.1\bin>j2ee -stop
Shutting down the J2EE server.
E:\j2sdkee1.2.1\bin>Hello ali_awan,
Upon looking at the output from the console, it looks like you had a problem when you ran setup under the petstore1.3 directory. The setup echoed several times:
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminToolBecause this class was not found, the latter deployment of the Petstore .ear file was not successful. To fix this, you will first need to successfully setup petstore1.3.
The NoClassDefFoundError indicates that the class files in the package com/sun/enterprise/tools/admin/AdminTool could not be located in the system CLASSPATH variable.
Please make sure that the directory that stores the package com/sun/enterprise/tools/admin/AdminTool is included in the system CLASSPATH. This should get rid of the errors during the create_jms_queues step. And hopefully this should alleviate the problems encountered during the deployment of the Petstore ear file.
For instructions how to set your CLASSPATH variable, please visit the following link:
http://java.sun.com/j2se/1.3/install-windows.html
Hope this helps!
Ming Chou
Developer Technical Support
http://www.sun.com/developers/support -
HI All,
I am trying to run WebLogic8.1 sp1 version of Petstore available at,
https://petstore.projects.dev2dev.bea.com/
in WebLogic9.1, unfortunately same domain config / binary can not run in 8.1 sp6 too.
WebLogic9.1 issues:
1. I have created JMS / JDBC resources by looking at config.xml. And XML Registry to some extent. WLS9.1 dont accept the PUBLICID given in Entity Spec Registry Entry same as in 8.1. So have to remove "," character from PUBLICID.
2. Dont know how URLResource can be configured in WLS9.1.
So hardcoded the URLResource in code OPC -> PurchaseOrderMDB.java. -> entityCatalogURL
3. Configured users admin and supplier in myrealm added them in group administrator.
3. Have to modify Catalog -> Item.java, added getAttribute1() method.
And changed Product.jsp,Item.jsp, Search.jsp -> ${item.attribute} to ${item.attribute1}.
Dont know why ${item.attribute} is not working?
Error says Item object does not have value for attribute though its there.
4. After all this I could create the ORDER in petstore webapp.
But OPC PurchaseOrderMDB throwing below error,
javax.ejb.EJBException: nested exception is: javax.xml.transform.TransformerException: java.io.FileNotFoundException: \com\sun\j2ee\blueprints\purchaseorder\rsrc\schemas\PurchaseOrder.dtd at com.sun.j2ee.blueprints.opc.ejb.PurchaseOrderMDB.onMessage(PurchaseOrderMDB.java:139)at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426) at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)at weblogic.work.ExecuteThread.execute ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
I am sure there is some problem in XMLRegistry Configuration, esp PUBLIC ID.
Can anyone tried runnig Petstore in WLS9.1? Help appreciated. If some one from WebLogic could guide, ready to put the WLS9.1 version in Petstore Project, Code Share.
Thanks in Advance.
Regards, JiteshHi,
I had the same problem deploying an application on the websphere 4.
I solved it by changing the application to a j2ee 1.2 application instead of 1.3.
Probably setting up websphere 5.0 will solve it.
Hope it helps.
Cheers,
Raymond -
J2EE 1.4 beta 2, W2K and Petstore hopeless
Hello
I can deploy the petstore application in J2EE 1.4 beta 2. It works, but only once. After a manual restart of the app server, the I get status 404.
I recognized a message in the deploy process.
reconfig:
[echo] Reconfiguring server server
[sun-appserv-admin] Executing: reconfig port 4848 host ursus --password xx -user admin server
[sun-appserv-admin[ Unable to read system environment. No system environment will be used
Perhaps someone has an idea what this means.
It is a long log available with exceptions stacks.
Starting J2EETM 1.4 Application Server Beta 2 ...
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:50:56:317 CEST][CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.1_02] from [Sun Microsystems Inc.]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:146 CEST][ADM0020:Following is the information about the JMX MBeanServer used:]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM0021:MBeanServer Implementation Name:[JMX]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM0022:MBeanServer Implementation Vendor:[Sun Microsystems]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM023:JMX Implementation Version:[1.2_r08]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM024:MBeanServer ID:[ursus_1059238261795]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:176 CEST][ADM025:MBeanServer Implementation Classname:[com.sun.jmx.mbeanserver.JmxMBeanServer]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:677 CEST][ADM0002:System MBean initialized:[ias:type=controller]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:707 CEST][ADM0002:System MBean initialized:[ias:type=configurator]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:737 CEST][ADM0001:MBeanServer initialized successfully]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:787 CEST][ADM0005:Timestamp files for configuration created for:[server]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:02:797 CEST][ADM0102: Starting a thread for tracking manual changes]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][26.Juli.2003 18:51:22:205 CEST][JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:/Programme/Sun/j2eesdk1.4_beta2/imq/bin].]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:23:887 CEST][S1AS AVK Instrumentation disabled]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.security][26.Juli.2003 18:51:23:907 CEST][SEC1143: Loading policy provider com.sun.enterprise.security.provider.util.PolicyWrapper.]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.transaction][26.Juli.2003 18:51:26:281 CEST][JTS5014: Recoverable JTS instance, serverId = [100]]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.resourceadapter][26.Juli.2003 18:51:40:942 CEST][RAR5060: Install JDBC Datasources ...]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:47:301 CEST][Satisfying Optional Packages dependencies...]>
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:48:533 CEST][ADM0016:Unable to determine java home. This suggests that you are using a version of J2EE plugin incompatible with administration server.]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][26.Juli.2003 18:51:48:923 CEST][[AutoDeploy] Enabling AutoDeployment service at :1059238308923]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:48:953 CEST][CORE5100:Loading system apps]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.deployment][26.Juli.2003 18:51:51:527 CEST][XML Error line : 39 The content of element type "sun-web-app" must match "(context-root?,security-role-mapping*,servlet*,session-config?,ejb-ref*,resource-ref*,resource-env-ref*,service-ref*,cache?,class-loader?,jsp-config?,locale-charset-info?,property*,message-destination*,webservice-description*)".]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:51:978 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@1a9b034]>
org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2142)
at org.apache.xerces.dom.AttrNSImpl.setName(AttrNSImpl.java:149)
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:110)
at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:1791)
at org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:660)
at com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttribute(DeploymentDescriptorNode.java:542)
at com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(LocalizedNode.java:77)
at com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisplayableComponentInfo(DisplayableComponentNode.java:56)
at com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleNode.java:104)
at com.sun.enterprise.deployment.node.ApplicationNode.writeDescriptor(ApplicationNode.java:132)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2EEDocumentBuilder.java:77)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:120)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
java.lang.IllegalArgumentException: Der Eingabeknoten darf f�r ein DOMSource f�r newTemplates nicht Null sein!
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:52:568 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.IllegalArgumentException: Der Eingabeknoten darf f�r ein DOMSource f�r newTemplates nicht Null sein!
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
... 11 more
]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:56:975 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@a8cd58]>
org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2142)
at org.apache.xerces.dom.AttrNSImpl.setName(AttrNSImpl.java:149)
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:110)
at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:1791)
at org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:660)
at com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttribute(DeploymentDescriptorNode.java:542)
at com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(LocalizedNode.java:77)
at com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisplayableComponentInfo(DisplayableComponentNode.java:56)
at com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleNode.java:104)
at com.sun.enterprise.deployment.node.ApplicationNode.writeDescriptor(ApplicationNode.java:132)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2EEDocumentBuilder.java:77)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:120)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
java.lang.IllegalArgumentException: Der Eingabeknoten darf f�r ein DOMSource f�r newTemplates nicht Null sein!
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:56:995 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.IllegalArgumentException: Der Eingabeknoten darf f�r ein DOMSource f�r newTemplates nicht Null sein!
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:346)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocumentBuilder.java:125)
at com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToString(J2EEDocumentBuilder.java:153)
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:158)
... 11 more
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:56:995 CEST][LDR5101: Could not get classpath
java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstore_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.loader.EJBClassPathUtils.getApplicationClassPath(EJBClassPathUtils.java:242)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspathList(EJBClassPathUtils.java:114)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspath(EJBClassPathUtils.java:87)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:63)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:035 CEST][LDR5006: Failed to load deployment descriptor
com.sun.enterprise.config.ConfigException: Failed to load deployment descriptor for: petstore
cause: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstore_1
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:270)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:230)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:69)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstore_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:253)
... 15 more
]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:045 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@196649c]>
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:045 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:159)
... 11 more
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:045 CEST][LDR5101: Could not get classpath
java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstoreadmin_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.loader.EJBClassPathUtils.getApplicationClassPath(EJBClassPathUtils.java:242)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspathList(EJBClassPathUtils.java:114)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspath(EJBClassPathUtils.java:87)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:63)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:065 CEST][LDR5006: Failed to load deployment descriptor
com.sun.enterprise.config.ConfigException: Failed to load deployment descriptor for: petstoreadmin
cause: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstoreadmin_1
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:270)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:230)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:69)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\petstoreadmin_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:253)
... 15 more
]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:105 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@a75004]>
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:105 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:152)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:159)
... 11 more
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:115 CEST][LDR5101: Could not get classpath
java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\supplier_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.loader.EJBClassPathUtils.getApplicationClassPath(EJBClassPathUtils.java:242)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspathList(EJBClassPathUtils.java:114)
at com.sun.enterprise.loader.EJBClassPathUtils.getEjbClasspath(EJBClassPathUtils.java:87)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:63)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
]>
<[SCHWERWIEGEND][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core.classloading][26.Juli.2003 18:51:57:115 CEST][LDR5006: Failed to load deployment descriptor
com.sun.enterprise.config.ConfigException: Failed to load deployment descriptor for: supplier
cause: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\supplier_1
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:270)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:230)
at com.sun.enterprise.server.ApplicationLoader.<init>(ApplicationLoader.java:69)
at com.sun.enterprise.server.TomcatApplicationLoader.<init>(TomcatApplicationLoader.java:57)
at com.sun.enterprise.server.pluggable.TomcatApplicationLoaderFactory.createApplicationLoader(TomcatApplicationLoaderFactory.java:32)
at com.sun.enterprise.server.ApplicationManager.getLoader(ApplicationManager.java:123)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:149)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:186)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:284)
at com.sun.enterprise.server.PEMain.run(PEMain.java:176)
at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.io.FileNotFoundException: D:\Programme\Sun\j2eesdk1.4_beta2\domains\domain1\server\applications\j2ee-apps\supplier_1
at com.sun.enterprise.deployment.archivist.FileArchive.open(FileArchive.java:38)
at com.sun.enterprise.instance.AppsManager.getAppDescriptor(AppsManager.java:253)
... 15 more
]>
<[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:115 CEST][ApplicationLoader com.sun.enterprise.server.TomcatApplicationLoader@766b42]>
<[WARNUNG][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][26.Juli.2003 18:51:57:115 CEST][CORE5016: Unexpected error occurred while loading applications
javax.management.MBeanException
at com.sun.enterprise.server.MgmtMBeansManager.createAppMBean(MgmtMBeansManager.java:165)
at com.sun.enterprise.server.ApplicationLoader.createRootMBean(ApplicationLoader.java:180)
at com.sun.enterprise.server.AI have not tried out Your advice. But what has this to do with my problem?
Is in the ant build process used US locale or what?
I have also this deploytool not save problem. But I don't want to change the locale only for the app server.
There must be other solutions. Personally it would interest me how someone can come to the locale setting.
Thanks
Urs -
JDBC Resultset Problem with ORACLE 10.1.0.2
Hello
I have a problem with Petstore GenericCatalogDAO. java. The problem is the behaviour of the resultset object when retrieving data from the database.Below are two synareos one that
works (when) hard coded and one that does not work when parameter values passed into the the result set.
1. The code the WORKS.
statement = connection.prepareStatement("select name from employee where a.name ='SMITH' order by name"
,ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
resultSet = statement.executeQuery();
resultSet.absolute(1);
String s = resultSet.getString(1);
The code that gives me a 'exhausted resultset' error which I think means no results
String[] parameterValues = new String[] { "SMITH" };
statement = connection.prepareStatement("select name from employee where a.name =? order by name ",
ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
for (int i = 0; i < parameterValues.length; i++) {
statement.setString(i + 1, parameterValues);
resultSet = statement.executeQuery();
resultSet.absolute(1);
String s = resultSet.getString(1);
There is obviously a problem using these named parametevalues with these preparedstatement resultset, Does anybody know anything about this and a fix for it????
Cheers. RogerRoger,
It's probably a mistake you made when posting your code, but your query string is incorrect it should be either:
select name from employee where name = 'SMITH' order by nameor
select a.name from employee a where a.name = 'SMITH' order by a.nameIn other words you have prefixed a column with a table alias but have not indicated a table alias in the query.
Also, shouldn't your code be:
for (int i = 0; i < parameterValues.length; i++) {
statement.setString(i + 1, parameterValues[ i ]);
}Or was the "[ i ]" part giving you trouble? (Since "[ i ]" -- without the spaces -- is treated as a text-formatting tag.)
While I didn't try your specific query, I have no problem using "PreparedStatment"s with parameters.
What is your environment? Mine is:
Oracle 10g (10.1.0.4) database on Linux (Red Hat)
JDK 1.4.2
ojdbc14.jar JDBC driver (latest version)
Good Luck,
Avi. -
How to cluster Petstore on WebLogic 8.1
I created a cluster with both managed servers running on the same machine as the admin server. But I could only deploy petstoreadmin.ear. With the other opc.ear, petstore.ear files, the delpoyment takes forever. I got some warnings like,
<XA resource [weblogic.jdbc.wrapper.JTSXAResourceImpl] has not responded in the last 120 seconds.>
I also got error like
<Error encountered while attempting to create default DBMS Table: 'lineitemEJB'. Error Text: 'Lock time out; try later.'.'>
First, is Petstore 1.3.1_02 cluster-able?
Second, what is the procedure to set it up?
I'd really appreciate any help on this."B" <[email protected]> wrote in message
news:4022cf75$[email protected]..
Tried using https://hostname:port/certificate but without success. Any
advice from anybody?
What error did you get? Did you deploy the certificate servlet? You may have
to deploy from
C:\bea810sp2\weblogic81\server\lib\certificate.war -
I am trying to install sample petstore application that comes with the Suns application server(linux version).
As mentioned in the petstore1.4/docs i performed the following
export $J2EE_HOME=/home/myDirectory/SUNWappserver
export PATH=$PATH:home/myDirectory/SUNWappserver/bin
export PETSTORE_HOME=$J2EE_HOME/sample/blueprints/petstore1.4
Then I started the pointbase server.
cd $J2EE_HOME/pointbase/tools/serveroption
startserver.sh
and application server
cd $J2EE_HOME/bin
asadmin start-domain domain1
then to build the petstore application
cd petstore_home/src
asant
everything worked fine till now. I get the message after building
BUILD SUCCESSFUL
Total time: 3 minutes 17 seconds
now as mentioned in the installation doc, I do asant deploy.
but the deployment hangs at verify_jdbc_connection_pool_common:
I am copying the asant deploy output here.
Am I missing some thing here. I was able to deploy the hello world application that comes
bundles with the application server.
Also, is there a alternate way to deploy applications without using asant deploy.
tia,
Amit
output of cd petstore_home/src;
asant deploy;
Buildfile: build.xml
build_cpath:
init_common:
init:
envpassword:
readpassword:
setpassword:
check_db:
checkPlatform:
configUnix:
[echo] on unix
configWindows:
configPlatform:
add.classpathsuffix:
init.oracleInet:
create-jdbc-connection-pools:
setup-jdbc-connection-pool-petstorepool:
[echo] Creating jdbc connection pool petstorepool
build_cpath:
init_common:
envhost:
readhost:
sethost:
envport:
readport:
setport:
envuser:
readuser:
setuser:
envpassword:
readpassword:
setpassword:
envinstance:
readinstance:
setinstance:
undate_env:
setup_env:
checkPlatform:
configUnix:
[echo] on unix
configWindows:
configPlatform:
verify_jdbc_connection_pool_common:Please check the connection pool and datasource in your server.
-
J2EE PetStore Application -- RDBMSException when starting server
Folks,
I'm trying to install Sun's J2EE PetStore application using the instructions at: http://developer.java.sun.com/developer/technicalArticles/Programming/deployathon2/BEAreadme.html#dlapp
When I attempt to start the WebLogic server using the "startPetStore.cmd" file, I receive the exception below. Has anyone got any helpful advice to offer?
Thanks,
-=Helen=-
Thu Sep 21 12:28:47 EDT 2000:<I> <WebLogicServer> Loaded License : C:/weblogic/license/WebLogicLicense.xml
Thu Sep 21 12:28:47 EDT 2000:<I> <WebLogicServer> Server loading from weblogic.class.path. EJB redeployment enabled.
Unable to initialize server: com.bea.estore.rdbmsrealm.RDBMSException: realm initialization failed, action 'DriverManager.getConnection', - with nested exception:
[SQL Exception: Failed to start database 'petStoreDB', see the next exception for details.]
fatal initialization exception
com.bea.estore.rdbmsrealm.RDBMSException: realm initialization failed, action 'DriverManager.getConnection', - with nested exception:
[SQL Exception: Failed to start database 'petStoreDB', see the next exception for details.]
at com.bea.estore.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:169)
at com.bea.estore.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:912)
at weblogic.utils.reuse.Pool.getInstance(Pool.java:57)
at com.bea.estore.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:115)
at com.bea.estore.rdbmsrealm.RDBMSRealm.getPermission(RDBMSRealm.java:515)
at weblogic.security.acl.CachingRealm.getPermission(CachingRealm.java:1698)
at weblogic.security.acl.CachingRealm.setupAcls(CachingRealm.java:757)
at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:706)
at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:564)
at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1747)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1084)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)I had the same problem. I ran this as a batch file to update the petStoreDB and it worked thereafter.
java -classpath c:\weblogic\eval\cloudscape\lib\cloudscape.jar;C:\jdk1.2.2;c:\weblogic\weblogic510sp3.jar;c:\weblogic\classes;c:\weblogic\lib\weblogicaux.jar;c:\weblogic\license;c:\weblogic\myserver\clientclasses; utils.Schema jdbc:cloudscape:petStoreDB;create=true COM.cloudscape.core.JDBCDriver -verbose c:\weblogic\petstore\WLSrc\db\petStore.ddl
Horance Chou <[email protected]> wrote:
I got the same problem before, and it's fixed by update new Schema.
use utils.Schema to update the petStoreDB with <petstore>\WLSrc\db\petstore.ddl
with Regrads.
Horance
Helen Seabold wrote:
Folks,
I'm trying to install Sun's J2EE PetStore application using the instructions at: http://developer.java.sun.com/developer/technicalArticles/Programming/deployathon2/BEAreadme.html#dlapp
When I attempt to start the WebLogic server using the "startPetStore.cmd" file, I receive the exception below. Has anyone got any helpful advice to offer?
Thanks,
-=Helen=-
Thu Sep 21 12:28:47 EDT 2000:<I> <WebLogicServer> Loaded License : C:/weblogic/license/WebLogicLicense.xml
Thu Sep 21 12:28:47 EDT 2000:<I> <WebLogicServer> Server loading from weblogic.class.path. EJB redeployment enabled.
Unable to initialize server: com.bea.estore.rdbmsrealm.RDBMSException: realm initialization failed, action 'DriverManager.getConnection', - with nested exception:
[SQL Exception: Failed to start database 'petStoreDB', see the next exception for details.]
fatal initialization exception
com.bea.estore.rdbmsrealm.RDBMSException: realm initialization failed, action 'DriverManager.getConnection', - with nested exception:
[SQL Exception: Failed to start database 'petStoreDB', see the next exception for details.]
at com.bea.estore.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:169)
at com.bea.estore.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:912)
at weblogic.utils.reuse.Pool.getInstance(Pool.java:57)
at com.bea.estore.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:115)
at com.bea.estore.rdbmsrealm.RDBMSRealm.getPermission(RDBMSRealm.java:515)
at weblogic.security.acl.CachingRealm.getPermission(CachingRealm.java:1698)
at weblogic.security.acl.CachingRealm.setupAcls(CachingRealm.java:757)
at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:706)
at weblogic.security.acl.CachingRealm.<init>(CachingRealm.java:564)
at weblogic.t3.srvr.T3Srvr.initializeSecurity(T3Srvr.java:1747)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1084)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55) -
Remote start petstore using NodeManager
Hi,
I am using weblogic 6.1 and remotely deployed pet store application on a different
machine using NodeManager. When I try to start the petStoreServer from local admin
console, I got following error:
Could not create pool connection. The DBMS driver exception was:
SQL Exception: Database 'petStore' not found.
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.l_(Unknown Source)
at c8e.k.j.n(Unknown Source)
at c8e.k.q.<init>(Unknown Source)
at c8e._b.e.<init>(Unknown Source)
at c8e._b.c.getNewLocalConnection(Unknown Source)
at c8e.k.v.connect(Unknown Source)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy0.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy47.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
Any hint?
Thanks,
Cathy
Covasoft, Inc.
1250 S. Capital of Texas Hwy.
Bldg. 1, Suite 240
Austin, Texas 78746
Office: 512.732.7860
Fax: 512.732.7832
Just add the property (-Dcloudscape....) as an extra argument to the jvm
startup parameters in the remote start tab of the remote server. That should
work as hte nodemanager just uses what settings are there in hte remote
start to create a server instance.
-Sabha
"Cathy" <[email protected]> wrote in message
news:[email protected]...
>
> Thanks for the quick reply. The directory for the petStore database is
there on
> the remote machine. I can't deloy datasource to the target server, since
the connection
> pool is not created yet due to the database error.
>
> The problem I found was that the remote server I started was not the one
from
> remote startPetStore.cmd, since the properties from that script is not
overrided
> or picked up ( including the cloudscape.system.home). I set up the remote
server
> from the admin server console "remote start". Ant hint to make sure the
admin
> server remote start use the correct script on the remote machine?
>
> Thanks,
> Cathy
>
>
>
> "Anand Byrappagari" <[email protected]> wrote:
> >Cathy,
> >
> > If you
> >have -Dcloudscape.system.home=<BEA_HOME>\samples\eval\cloudscape\data
> >set
> >then is there a directory called
> ><BEA_HOME>\samples\eval\cloudscape\data\petStore present on the remote
> >server machine? If not you have not created the petStore database.
> >
> > The only other thing I can think of is that the connection
> >pool/datasource are not targeted to the remote server but these errors
> >usually throw a different exception.
> >
> >-- Anand
> >
> >
> >"Cathy" <[email protected]> wrote in message
> >news:[email protected]...
> >>
> >> Thanks for the reply. Actually, I have set this property for the remote
> >server
> >> with the right path. But I still got the same error. Any other hints?
> >>
> >> Thanks,
> >> Cathy
> >>
> >> "Sabha" <[email protected]> wrote:
> >> >Make sure you have set the cloudscape home directory in the startup
> >script:
> >> >
> >> >-Dcloudscape.system.home=<BEA_HOME>\samples\eval\cloudscape\data
> >> >
> >> >-Sabha
> >> >
> >> >
> >> >"Cathy" <[email protected]> wrote in message
> >> >news:[email protected]...
> >> >>
> >> >> Hi,
> >> >>
> >> >> I am using weblogic 6.1 and remotely deployed pet store application
> >> >on a
> >> >different
> >> >> machine using NodeManager. When I try to start the petStoreServer
> >from
> >> >local admin
> >> >> console, I got following error:
> >> >>
> >> >> Could not create pool connection. The DBMS driver exception was:
> >> >> SQL Exception: Database 'petStore' not found.
> >> >> at c8e.k.j.l_(Unknown Source)
> >> >> at c8e.k.j.l_(Unknown Source)
> >> >> at c8e.k.j.n(Unknown Source)
> >> >> at c8e.k.q.<init>(Unknown Source)
> >> >> at c8e._b.e.<init>(Unknown Source)
> >> >> at c8e._b.c.getNewLocalConnection(Unknown Source)
> >> >> at c8e.k.v.connect(Unknown Source)
> >> >> at
> >>
>
>>weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
o
> >n
> >> >EnvFactory.java:193)
> >> >> at
> >>
>
>>weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
o
> >n
> >> >EnvFactory.java:134)
> >> >> at
> >>
>
>>weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
> >j
> >> >ava:698)
> >> >> at
> >>
>
>>weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:2
8
> >2
> >> >)
> >> >> at
> >>
>
>>weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:6
2
> >3
> >> >)
> >> >> at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
> >> >> at
> >>
>
>>weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deploymen
t
> >T
> >> >arget.java:329)
> >> >> at
> >>
>
>>weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployme
n
> >t
> >> >Target.java:279)
> >> >> at
> >>
>
>>weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments
> >D
> >> >eploymentTarget.java:233)
> >> >> at
> >>
>
>>weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deplo
y
> >m
> >> >entTarget.java:193)
> >> >> at java.lang.reflect.Method.invoke(Native Method)
> >> >> at
> >>
>
>>weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
p
> >l
> >> >..java:636)
> >> >> at
> >>
>
>>weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
> >6
> >> >21)
> >> >> at
> >>
>
>>weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
e
> >a
> >> >nImpl.java:359)
> >> >> at
> >>
>com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
> >> >> at
> >>
>com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
> >> >> at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> >> >> at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> >> >> at $Proxy0.updateDeployments(Unknown Source)
> >> >> at
> >>
>
>>weblogic.management.configuration.ServerMBean_CachingStub.updateDeployment
s
> >(
> >> >ServerMBean_CachingStub.java:2761)
> >> >> at
> >>
>
>>weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Ap
p
> >l
> >> >icationManager.java:370)
> >> >> at
> >>
>
>>weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationMana
g
> >e
> >> >r.java:160)
> >> >> at java.lang.reflect.Method.invoke(Native Method)
> >> >> at
> >>
>
>>weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
p
> >l
> >> >..java:636)
> >> >> at
> >>
>
>>weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
> >6
> >> >21)
> >> >> at
> >>
>
>>weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
e
> >a
> >> >nImpl.java:359)
> >> >> at
> >>
>com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
> >> >> at
> >>
>com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
> >> >> at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> >> >> at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> >> >> at $Proxy47.start(Unknown Source)
> >> >> at
> >>
>
>>weblogic.management.configuration.ApplicationManagerMBean_CachingStub.star
t
> >(
> >> >ApplicationManagerMBean_CachingStub.java:480)
> >> >> at
weblogic.management.Admin.startApplicationManager(Admin.java:1180)
> >> >> at weblogic.management.Admin.finish(Admin.java:590)
> >> >> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
> >> >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
> >> >>
> >> >> Any hint?
> >> >>
> >> >> Thanks,
> >> >> Cathy
> >> >>
> >> >> Covasoft, Inc.
> >> >> 1250 S. Capital of Texas Hwy.
> >> >> Bldg. 1, Suite 240
> >> >> Austin, Texas 78746
> >> >> Office: 512.732.7860
> >> >> Fax: 512.732.7832
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >
> >
>
-
Petstore throws populateServlet error with Oracle thin driver
When i point connection pool to Oracle database, i get the following error. The
data is populated in the database, looks like when petstore is enumerating db
tables and make sure all tables exist, this error is happening. Some how, database
metadata coming as NULL. Has anybody tried petstore with Oracle JDBC driver?
thanks,
PopulateServlet Error:
java.lang.NullPointerException java.lang.NullPointerException at com.sun.j2ee.blueprints.tools.populate.web.PopulateServlet.checkTables(PopulateServlet.java:276)
at com.sun.j2ee.blueprints.tools.populate.web.PopulateServlet.doGet(PopulateServlet.java:127)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)I believe that you do not have weblogicaux.jar in your classpath.
-Selvan
Laurie Cohen wrote:
Im using Solaris 2.7 with WLS 5.1.0 and Commerce Server 2.0.1 with
current service packs on both. JDK 1.2.1_04 and the Oracle thin driver
(classes111.zip which I am told is the only one supported in this
configuration). Has anyone seen this problem? Is it that the driver is
using 1.1 and I only have 1.2 installed?
devapp01% java -classpath
/usr/local/weblogic/classes:/usr/local/weblogic/license utils.t3dbping
t3://localhost:7601 username password "" oracle.jdbc.driver.OracleDriver
jdbc:oracle:thin:@10.200.201.110:1521:q01c
Connecting to WebLogic with the WebLogic JDBC Driver
Exception in thread "main" java.lang.NoClassDefFoundError:
com/sun/java/util/collections/ArrayList
at weblogic.kernel.Kernel.declareProperties(Kernel.java:253)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:107)
at weblogic.common.T3Client.<init>(T3Client.java:218)
at weblogic.common.T3Client.<init>(T3Client.java:269)
at weblogic.common.T3Client.<init>(T3Client.java:323)
at weblogic.jdbcbase.t3.Driver.connect(Driver.java:121)
at java.sql.DriverManager.getConnection(Compiled Code)
at java.sql.DriverManager.getConnection(DriverManager.java:106)
at utils.t3dbping.main(t3dbping.java:115)
Thanks,
Laurie -
Petstore Oracle Database Exception
To whom it may concern,
I recently installed WebLogic 7.0. It worked just fine with the pointbase database
connection. The petstore example worked.. As soon as I began setting up weblogic
with an Oracle database, I began running into problems. Here is what I do know
- Connection to the Database works
- utils.dbping to database works
- Configuring Weblogic to use database connection fails.
Currently, I am stuck trying to find why the following exception is being thrown:
Unable to deploy EJB: ContactInfoEJB from suppPOEjb.jar:
weblogic.ejb20.WLDeploymentException: Incorrect DataSource type
detected. The DataSource with JNDI name 'datasource-petstoresupplierPool', specified
in the RDBMS deployment
descriptor for the EJB 'ContactInfoEJB', is not a TXDataSource.
The EJB Container requires a TXDataSource to be specified for
transactions to be managed correctly.
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyTXDataSource(R
DBMSPersistenceManager.java:977)
If you can shed some light on why this might be happening or point me to documentation
that could shed light on how to properly configure the petstore example, that would
be fabulous. I have included the installation notes we performed to this point.
We will continue to locate information regarding this issue. Thank you in advance
for your help.
Dan
<Installing BEA Web Logic 7.0>
[Administrator]
<Pre-Requisites>
- Install Oracle 8i 8.1.7 Database Client
(Note: Place the "weblogic700_win.exe" binary into c:\temp on the target machine)
- Double click "c:\temp\weblogic700_win.exe"
<BEA Installation Framework - Weblogic Platform 7.0 - Welcome>
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - BEA License Agreement>
- Do you agree with the terms of the license? Yes
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - BEA Home Directory>
- Select "Create a new BEA Home"
- BEA Home Directory: c:\bea
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - Choose Install Type>
- Select "Typical Installation"
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - Choose Product Directory>
- Product Installation Directory: c:\bea\weblogic700
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - Install Complete>
- Click the "Done" button
<Configure the Database properties correctly>
<Test connection to the Database>
c:\oracle\ora81\bin> sqlplus petstore70/petstore70@octqa1
<Update the Environment Path>
- Click "Start -> Settings -> Control Panel"
<Control Panel>
- Double Click "System"
<System Properties>
- Click the "Advanced" tab
- Click the "Environment Variables" button
<Environment Variables>
- Double click Variable "Path" beneath "System variables"
<Edit System Variable>
- Variable Name: Path
- Append ";c:\bea\weblogic700\server\bin\oci817_8;c:\oracle\ora81\bin" to the end
of "Variable Value"
- Click the "OK" button
<Test the Database Connection from WebLogic>
c:\bea\weblogic700\server\bin> setWLSEnv.cmd
c:\bea\weblogic700\server\bin> set path=c:\bea\wlserver700\server\bin\oci817_8;%PATH%
c:\bea\weblogic700\server\bin> java utils.dbping ORACLE petstore70 petstore70 octqa1
<Follow the Instructions for updating the PetStore to enable a different database>
- Read and Execute: c:\bea\weblogic700\samples\server\src\petstore\petstore.html
<Execute the build command>
c:\bea\weblogic700\samples\server\config\examples> setExamplesEnv
c:\bea\weblogic700\samples\server\src\petstore\src> ant
<Verify the *ear files exist>
c:\bea> dir c:\bea\weblogic700\samples\server\src\petstore\src\apps\admin\build
c:\bea> dir c:\bea\weblogic700\samples\server\src\petstore\src\apps\opc\build
c:\bea> dir c:\bea\weblogic700\samples\server\src\petstore\src\apps\petstore\build
c:\bea> dir c:\bea\weblogic700\samples\server\src\petstore\src\apps\supplier\build
<Run the Examples Server>
c:\bea\weblogic700\samples\server\config\examples> startExamplesServer.cmd
<Configure the petstore Database JDBC petstore pool>
- Visit http://ibs26:7001/console
<Administration Console - BEA WebLogic Server 7.0>
- Username: weblogic
- Password: weblogic
- Click the "Sign In" button
<WebLogic Server Console>
- Select "petstore -> Services -> JDBC -> Connection Pools"
- Click the "Configure a new JDBC Connection Pool"
<examples: JDBC Connection ... Create a new JDBC Connection Pool>
- Select "Configuration:General"
- Name: petstorePool
- URL: jdbc:weblogic:oracle:OCTQA1
- Driver ClassName: weblogic.jdbc.oci.Driver
(Note: Make sure the following user was added to the oracle database)
- Properties: user=petstore70
- Password: petstore70
- Click the "Create" button
<examples: JDBC Connection ... petstorePool>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<WebLogic Server Console>
- Select "petstore -> Services -> JDBC -> Connection Pools"
- Click the "Configure a new JDBC Connection Pool"
<examples: JDBC Connection ... Create a new JDBC Connection Pool>
- Select "Configuration:General"
- Name: petstoreopcPool
- URL: jdbc:weblogic:oracle:OCTQA1
- Driver ClassName: weblogic.jdbc.oci.Driver
(Note: Make sure the following user was added to the oracle database)
- Properties: user=petstore70opc
- Password: petstore70opc
- Click the "Create" button
<examples: JDBC Connection ... petstorePool>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<WebLogic Server Console>
- Select "petstore -> Services -> JDBC -> Connection Pools"
- Click the "Configure a new JDBC Connection Pool"
<examples: JDBC Connection ... Create a new JDBC Connection Pool>
- Select "Configuration:General"
- Name: petstoresupplierPool
- URL: jdbc:weblogic:oracle:OCTQA1
- Driver ClassName: weblogic.jdbc.oci.Driver
(Note: Make sure the following user was added to the oracle database)
- Properties: user=petstore70supplier
- Password: petstore70supplier
- Click the "Create" button
<examples: JDBC Connection ... petstorePool>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Data Sources>
- Select "petstore -> Services -> JDBC -> Data Sources"
- Click the "Configure a new JDBC Data Source"
<examples.. JDBC Data Sources.. Create a new JDBCDataSource...>
- Name: PetstoreDataSource
- JNDI Name: datasource-petstorePool
- Pool Name: petstorePool
- Click the "Create" button
<examples.. JDBC Data Sources.. PetstoreDataSource...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Data Sources>
- Select "petstore -> Services -> JDBC -> Data Sources"
- Click the "Configure a new JDBC Data Source"
<examples.. JDBC Data Sources.. Create a new JDBCDataSource...>
- Name: PetstoreOPCDataSource
- JNDI Name: datasource-petstoreopcPool
- Pool Name: petstoreopcPool
- Click the "Create" button
<examples.. JDBC Data Sources.. PetstoreOPCDataSource...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Data Sources>
- Select "petstore -> Services -> JDBC -> Data Sources"
- Click the "Configure a new JDBC Data Source"
<examples.. JDBC Data Sources.. Create a new JDBCDataSource...>
- Name: PetstoreSupplierDataSource
- JNDI Name: datasource-petstoresupplierPool
- Pool Name: petstoresupplierPool
- Click the "Create" button
<examples.. JDBC Data Sources.. PetstoreSupplierDataSource...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Data Sources>
- Select "petstore -> Services -> JDBC -> Data Sources"
- Click the "Configure a new JDBC Data Source"
<examples.. JDBC Data Sources.. Create a new JDBCDataSource...>
- Name: CatalogDataSource
- JNDI Name: jdbc.CatalogDataSource
- Pool Name: petstorePool
- Click the "Create" button
<examples.. JDBC Data Sources.. CatalogDataSource...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Connection Factories>
- Select "petstore -> Services -> JMS -> Connection Factories"
- Click the "Configure a New JMS Connection Factory."
<examples... JMS Connection F.... Create a new JMSConnectionFactory>
- Click the "General" tab
- Name: petstoreQueueConnectionFactory
- JNDIName: jms.JPS_MY_QUEUE
- Click the "Create" button
<examples.. JMS Connection F... petstoreQueueCon...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Connection Factories>
- Select "petstore -> Services -> JMS -> Connection Factories"
- Click the "Configure a New JMS Connection Factory."
<examples... JMS Connection F.... Create a new JMSConnectionFactory>
- Click the "General" tab
- Name: petstoreTopicConnectionFactory
- JNDIName: jms.MyTopicConnectionFactory
- Click the "Create" button
<examples.. JMS Connection F... petstoreTopicCon...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Move the EAR Files to the Examples Domain>
c:\bea\weblogic700\samples\server\src\petstore\src\apps\admin\build> copy *ear ..\..\..\..\..\..\config\examples\applications
c:\bea\weblogic700\samples\server\src\petstore\src\apps\opc\build> copy *ear ..\..\..\..\..\..\config\examples\applications
c:\bea\weblogic700\samples\server\src\petstore\src\apps\petstore\build> copy *ear
.\..\..\..\..\..\config\examples\applications
c:\bea\weblogic700\samples\server\src\petstore\src\apps\supplier\build> copy *ear
.\..\..\..\..\..\config\examples\applications
<Restart the weblogic Examples server>
c:\bea\weblogic700\samples\server\config\examples> startExamplesServer.cmd
<Visit the Petstore Application
- Visit http://ibs26:7001/petstore/index.jsp
<Notes on install>
- The following is being thrown in the examples server:
Unable to deploy EJB: ContactInfoEJB from suppPOEjb.jar:
weblogic.ejb20.WLDeploymentException: Incorrect DataSource type detected. The Da
taSource with JNDI name 'datasource-petstoresupplierPool', specified in the RDBM
S deployment descriptor for the EJB 'ContactInfoEJB', is not a TXDataSource. The
EJB Container requires a TXDataSource to be specified for transactions to be ma
naged correctly.
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyTXDataSource(R
DBMSPersistenceManager.java:977)
- At present, there is no solution to this issueTo whom it may concern,
I recently installed WebLogic 7.0. It worked just fine with the pointbase database
connection. The petstore example worked.. As soon as I began setting up weblogic
with an Oracle database, I began running into problems. Here is what I do know
- Connection to the Database works
- utils.dbping to database works
- Configuring Weblogic to use database connection fails.
Currently, I am stuck trying to find why the following exception is being thrown:
Unable to deploy EJB: ContactInfoEJB from suppPOEjb.jar:
weblogic.ejb20.WLDeploymentException: Incorrect DataSource type
detected. The DataSource with JNDI name 'datasource-petstoresupplierPool', specified
in the RDBMS deployment
descriptor for the EJB 'ContactInfoEJB', is not a TXDataSource.
The EJB Container requires a TXDataSource to be specified for
transactions to be managed correctly.
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyTXDataSource(R
DBMSPersistenceManager.java:977)
If you can shed some light on why this might be happening or point me to documentation
that could shed light on how to properly configure the petstore example, that would
be fabulous. I have included the installation notes we performed to this point.
We will continue to locate information regarding this issue. Thank you in advance
for your help.
Dan
<Installing BEA Web Logic 7.0>
[Administrator]
<Pre-Requisites>
- Install Oracle 8i 8.1.7 Database Client
(Note: Place the "weblogic700_win.exe" binary into c:\temp on the target machine)
- Double click "c:\temp\weblogic700_win.exe"
<BEA Installation Framework - Weblogic Platform 7.0 - Welcome>
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - BEA License Agreement>
- Do you agree with the terms of the license? Yes
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - BEA Home Directory>
- Select "Create a new BEA Home"
- BEA Home Directory: c:\bea
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - Choose Install Type>
- Select "Typical Installation"
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - Choose Product Directory>
- Product Installation Directory: c:\bea\weblogic700
- Click the "Next" button
<BEA Installation Framework - Weblogic Platform 7.0 - Install Complete>
- Click the "Done" button
<Configure the Database properties correctly>
<Test connection to the Database>
c:\oracle\ora81\bin> sqlplus petstore70/petstore70@octqa1
<Update the Environment Path>
- Click "Start -> Settings -> Control Panel"
<Control Panel>
- Double Click "System"
<System Properties>
- Click the "Advanced" tab
- Click the "Environment Variables" button
<Environment Variables>
- Double click Variable "Path" beneath "System variables"
<Edit System Variable>
- Variable Name: Path
- Append ";c:\bea\weblogic700\server\bin\oci817_8;c:\oracle\ora81\bin" to the end
of "Variable Value"
- Click the "OK" button
<Test the Database Connection from WebLogic>
c:\bea\weblogic700\server\bin> setWLSEnv.cmd
c:\bea\weblogic700\server\bin> set path=c:\bea\wlserver700\server\bin\oci817_8;%PATH%
c:\bea\weblogic700\server\bin> java utils.dbping ORACLE petstore70 petstore70 octqa1
<Follow the Instructions for updating the PetStore to enable a different database>
- Read and Execute: c:\bea\weblogic700\samples\server\src\petstore\petstore.html
<Execute the build command>
c:\bea\weblogic700\samples\server\config\examples> setExamplesEnv
c:\bea\weblogic700\samples\server\src\petstore\src> ant
<Verify the *ear files exist>
c:\bea> dir c:\bea\weblogic700\samples\server\src\petstore\src\apps\admin\build
c:\bea> dir c:\bea\weblogic700\samples\server\src\petstore\src\apps\opc\build
c:\bea> dir c:\bea\weblogic700\samples\server\src\petstore\src\apps\petstore\build
c:\bea> dir c:\bea\weblogic700\samples\server\src\petstore\src\apps\supplier\build
<Run the Examples Server>
c:\bea\weblogic700\samples\server\config\examples> startExamplesServer.cmd
<Configure the petstore Database JDBC petstore pool>
- Visit http://ibs26:7001/console
<Administration Console - BEA WebLogic Server 7.0>
- Username: weblogic
- Password: weblogic
- Click the "Sign In" button
<WebLogic Server Console>
- Select "petstore -> Services -> JDBC -> Connection Pools"
- Click the "Configure a new JDBC Connection Pool"
<examples: JDBC Connection ... Create a new JDBC Connection Pool>
- Select "Configuration:General"
- Name: petstorePool
- URL: jdbc:weblogic:oracle:OCTQA1
- Driver ClassName: weblogic.jdbc.oci.Driver
(Note: Make sure the following user was added to the oracle database)
- Properties: user=petstore70
- Password: petstore70
- Click the "Create" button
<examples: JDBC Connection ... petstorePool>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<WebLogic Server Console>
- Select "petstore -> Services -> JDBC -> Connection Pools"
- Click the "Configure a new JDBC Connection Pool"
<examples: JDBC Connection ... Create a new JDBC Connection Pool>
- Select "Configuration:General"
- Name: petstoreopcPool
- URL: jdbc:weblogic:oracle:OCTQA1
- Driver ClassName: weblogic.jdbc.oci.Driver
(Note: Make sure the following user was added to the oracle database)
- Properties: user=petstore70opc
- Password: petstore70opc
- Click the "Create" button
<examples: JDBC Connection ... petstorePool>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<WebLogic Server Console>
- Select "petstore -> Services -> JDBC -> Connection Pools"
- Click the "Configure a new JDBC Connection Pool"
<examples: JDBC Connection ... Create a new JDBC Connection Pool>
- Select "Configuration:General"
- Name: petstoresupplierPool
- URL: jdbc:weblogic:oracle:OCTQA1
- Driver ClassName: weblogic.jdbc.oci.Driver
(Note: Make sure the following user was added to the oracle database)
- Properties: user=petstore70supplier
- Password: petstore70supplier
- Click the "Create" button
<examples: JDBC Connection ... petstorePool>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Data Sources>
- Select "petstore -> Services -> JDBC -> Data Sources"
- Click the "Configure a new JDBC Data Source"
<examples.. JDBC Data Sources.. Create a new JDBCDataSource...>
- Name: PetstoreDataSource
- JNDI Name: datasource-petstorePool
- Pool Name: petstorePool
- Click the "Create" button
<examples.. JDBC Data Sources.. PetstoreDataSource...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Data Sources>
- Select "petstore -> Services -> JDBC -> Data Sources"
- Click the "Configure a new JDBC Data Source"
<examples.. JDBC Data Sources.. Create a new JDBCDataSource...>
- Name: PetstoreOPCDataSource
- JNDI Name: datasource-petstoreopcPool
- Pool Name: petstoreopcPool
- Click the "Create" button
<examples.. JDBC Data Sources.. PetstoreOPCDataSource...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Data Sources>
- Select "petstore -> Services -> JDBC -> Data Sources"
- Click the "Configure a new JDBC Data Source"
<examples.. JDBC Data Sources.. Create a new JDBCDataSource...>
- Name: PetstoreSupplierDataSource
- JNDI Name: datasource-petstoresupplierPool
- Pool Name: petstoresupplierPool
- Click the "Create" button
<examples.. JDBC Data Sources.. PetstoreSupplierDataSource...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Data Sources>
- Select "petstore -> Services -> JDBC -> Data Sources"
- Click the "Configure a new JDBC Data Source"
<examples.. JDBC Data Sources.. Create a new JDBCDataSource...>
- Name: CatalogDataSource
- JNDI Name: jdbc.CatalogDataSource
- Pool Name: petstorePool
- Click the "Create" button
<examples.. JDBC Data Sources.. CatalogDataSource...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Connection Factories>
- Select "petstore -> Services -> JMS -> Connection Factories"
- Click the "Configure a New JMS Connection Factory."
<examples... JMS Connection F.... Create a new JMSConnectionFactory>
- Click the "General" tab
- Name: petstoreQueueConnectionFactory
- JNDIName: jms.JPS_MY_QUEUE
- Click the "Create" button
<examples.. JMS Connection F... petstoreQueueCon...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Create the Connection Factories>
- Select "petstore -> Services -> JMS -> Connection Factories"
- Click the "Configure a New JMS Connection Factory."
<examples... JMS Connection F.... Create a new JMSConnectionFactory>
- Click the "General" tab
- Name: petstoreTopicConnectionFactory
- JNDIName: jms.MyTopicConnectionFactory
- Click the "Create" button
<examples.. JMS Connection F... petstoreTopicCon...>
- Click the "Targets" tab
- Click the "Servers" tab
- Select "examplesServer"
- Click the ">" button to add it to the chosen list
- Click the "Apply" button
<Move the EAR Files to the Examples Domain>
c:\bea\weblogic700\samples\server\src\petstore\src\apps\admin\build> copy *ear ..\..\..\..\..\..\config\examples\applications
c:\bea\weblogic700\samples\server\src\petstore\src\apps\opc\build> copy *ear ..\..\..\..\..\..\config\examples\applications
c:\bea\weblogic700\samples\server\src\petstore\src\apps\petstore\build> copy *ear
.\..\..\..\..\..\config\examples\applications
c:\bea\weblogic700\samples\server\src\petstore\src\apps\supplier\build> copy *ear
.\..\..\..\..\..\config\examples\applications
<Restart the weblogic Examples server>
c:\bea\weblogic700\samples\server\config\examples> startExamplesServer.cmd
<Visit the Petstore Application
- Visit http://ibs26:7001/petstore/index.jsp
<Notes on install>
- The following is being thrown in the examples server:
Unable to deploy EJB: ContactInfoEJB from suppPOEjb.jar:
weblogic.ejb20.WLDeploymentException: Incorrect DataSource type detected. The Da
taSource with JNDI name 'datasource-petstoresupplierPool', specified in the RDBM
S deployment descriptor for the EJB 'ContactInfoEJB', is not a TXDataSource. The
EJB Container requires a TXDataSource to be specified for transactions to be ma
naged correctly.
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyTXDataSource(R
DBMSPersistenceManager.java:977)
- At present, there is no solution to this issue -
I tried to install the petstore with oracle.
I'm using the following versions:
j2eesdk-1_4_01-samples.zip
j2sdk-1_4_2_04-linux-i586.bin
sjsas_pe-8_0_0_01-linux.bin
oracle10i
when populating the database I always got sql-exceptions.
By try and error I fixed the problem by replacing every occurence
of 'EJBTABLE' with 'EJB' in the table-names in the sql-scripts
in petstore1.4/src/sql/.
Can anyone else confirm that these sql-scripts are wrong ?
thanks EdmundI checked samples/blueprints/petstore1.4/docs/configuring.html:
it contains entries for pointbase and oracle. The entries look ok
to me.
I got the following exception:
[#|2004-06-23T13:00:12.823+0200|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=12;|
javax.ejb.EJBException
at com.sun.ejb.containers.BaseContainer.processSystemException(BaseContainer.java:2697)
at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2603)
at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2411)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:763)
at com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:197)
at $Proxy48.findByPrimaryKey(Unknown Source)
at com.sun.j2ee.blueprints.petstore.tools.populate.UserPopulator.createUser(Unknown Source)
at com.sun.j2ee.blueprints.petstore.tools.populate.UserPopulator.access$000(Unknown Source)
at com.sun.j2ee.blueprints.petstore.tools.populate.UserPopulator$1.create(Unknown Source)
at com.sun.j2ee.blueprints.petstore.tools.populate.XMLDBHandler.endElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:546)
at org.apache.xerces.impl.dtd.XMLNSDTDValidator.endNamespaceScope(XMLNSDTDValidator.java:257)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1992)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:902)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:533)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1560)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:355)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:539)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:595)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1125)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at com.sun.j2ee.blueprints.petstore.tools.populate.PopulateServlet.populate(Unknown Source)
at com.sun.j2ee.blueprints.petstore.tools.populate.PopulateServlet.doPost(Unknown Source)
at com.sun.j2ee.blueprints.petstore.tools.populate.PopulateServlet.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:748)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
at com.sun.j2ee.blueprints.signon.web.SignOnFilter.doFilter(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:218)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
at com.sun.j2ee.blueprints.encodingfilter.web.EncodingFilter.doFilter(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:218)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:272)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
: at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sun.jdo.api.persistence.support.JDODataStoreException: JDO76400: Got a JDBC SQLException while executing the SQL statement:
SQL statement<select t0."PASSWORD", t0."USERNAME" from "USEREJB" t0 where t0."USERNAME" = ?> with input values:java.lang.String:j2ee.
Please examine the SQLException for more information.
NestedException: java.sql.SQLException: ORA-00942: table or view does not exist
at com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.handleSQLException(SQLStoreManager.java:851)
at com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeQuery(SQLStoreManager.java:484)
at com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.retrieve(SQLStoreManager.java:377)
at com.sun.jdo.spi.persistence.support.sqlstore.SQLStateManager.reload(SQLStateManager.java:1101)
at com.sun.jdo.spi.persistence.support.sqlstore.SQLStateManager.loadForRead(SQLStateManager.java:4023)
at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.getObjectById(PersistenceManagerImpl.java:618)
at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerWrapper.getObjectById(PersistenceManagerWrapper.java:245)
at com.sun.j2ee.blueprints.signon.user.ejb.UserEJB_1182430765_ConcreteImpl.ejbFindByPrimaryKey(UserEJB_1182430765_ConcreteImpl.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:140)
at com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:182)
... 109 more
|#]
Edmund
Maybe you are looking for
-
Setting up a small business network using mac and windows pcs
Setting up a small business network using mac and windows??
-
Problem in Selecting elements in XSLT
Hi, I have the following XML. <asx:values> <Seg1 A="a" B="b> <Seg1 A="c" B="d"> <Seg2 X="a" Y="b> <Seg2 X="c" Y="d"> </asx:values> Now i have the following XSLT. <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sapxsl="http://www
-
Find a package/class in *.jar in-or-under a directory?
Folks, Please, has anyone got a Java equivalent of: find . -name '*.jar' -exec fgrep -l "the.package.ClassName" {} \;That is: find all occurrences of "the.package.ClassName.class" in all JAR files located in-or-under the present working directory. My
-
Disabling shipping details for configurator model item in istore.
Hi all, I am working in istore implementation process in R12. I got some Issues while using using Configurator ATO model item in istore. If we disable the"Shippable" flag for single item means, it was "NON-Shippable" item, And we never get any shippi
-
Iphone 5s top part of screen visible leds. Am I paranoid?
Guys, i have a problem with my phone. There are visible darker spots on the top of the screen visible on a white or orange background, that are not visible on a friends iphone 5s. The problem is more evident when tilting the phone, also you can see i