Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SQLException - FOR UPDATE clause allowed only for DECLARE CURSOR

160 views
Skip to first unread message

Madhu

unread,
Mar 9, 2001, 12:27:38 AM3/9/01
to

I see the following error trying to run the examples for JMS (weblogic5.1).
Any help is greatly appreciated.

Thanks,
Madhu

Thu Mar 08 20:53:14 PST 2001:<I> <JMS> java.sql.SQLException: Line
2: FOR UPDATE clause allowed only for DECLARE CURSOR. Severity
15, State 2, Procedure 'BRONCO null', Line 2
at weblogic.jdbcbase.mssqlserver4.TdsStatement.processWarning(Unknown
Source)
at weblogic.jdbcbase.mssqlserver4.TdsStatement.parseMsWarning(Unknown
Source)
at weblogic.jdbcbase.mssqlserver4.TdsStatement.getMoreResults(Unknown
Source)
at weblogic.jdbcbase.mssqlserver4.TdsStatement.execute(Unknown
Source)
at weblogic.jdbcbase.mssqlserver4.TdsStatement.executeQuery(Unknown
Source)
at weblogic.jdbcbase.mssqlserver4.TdsStatement.executeQuery(Unknown
Source)
at weblogic.jdbc.pool.PreparedStatement.executeQuery(PreparedStatement.java:48)
at weblogic.jms.server.JDBCStore.reserveDbKeys(JDBCStore.java:1003)
at weblogic.jms.server.JDBCStore.storeDestination(JDBCStore.java:387)
at weblogic.jms.server.JMSRegistry.addDestination(JMSRegistry.java:494)
at weblogic.jms.server.JMSRegistry.addDestination(JMSRegistry.java:471)
at weblogic.jms.server.JMSManager.findOrCreateTopic(JMSManager.java:630)
at weblogic.jms.server.TopicSessionState.createTopic(TopicSessionState.java:23)
at weblogic.jms.common.WLSkely1u2v1o3yc724g271r7304w243q64.invoke(WLSkely1u2v1o3yc724g271r7304w243q64.java:164)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:69)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Lisa Popp

unread,
Mar 9, 2001, 11:54:59 AM3/9/01
to

Are you using BEA's jDriver/MSSQLServer4 Type 4 JDBC driver for 5.1.0?
Are you running SP8? What does your connectionPool configuration look like in your weblogic.properties file? What jms
example are you trying to run?

-Lisa

Madhu

unread,
Mar 9, 2001, 1:47:02 PM3/9/01
to

Sorry, I thought that the error was so vague that if anyone had
looked at it before they would remember it and I could get a clue.
The details are below -

The configuration is 5.1 with SP8
Yes. I am using BEA's jDriver/MSSQLServer4 driverYes.
I am trying the JMS Trader example provided with 5.1

The connection pool configuration is below -
weblogic.jms.connectionPool=jmsPool

weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet

weblogic.jdbc.connectionPool.jmsPool=\
url=jdbc:weblogic:mssqlserver4:Rel6_0@localhost:1433,\
driver=weblogic.jdbc.mssqlserver4.Driver,\
initialCapacity=1,\
maxCapacity=5,\
capacityIncrement=2,\
props=user=mnarasa;password=;server=bronco

The startup has the following -
Fri Mar 09 10:39:09 PST 2001:<I> <JDBC Pool> Connection for pool
"jmsPool" created.
Fri Mar 09 10:39:10 PST 2001:<I> <JMS> Table scavenger initialized
Fri Mar 09 10:39:10 PST 2001:<I> <JMS> Initializing from backing
store
Fri Mar 09 10:39:10 PST 2001:<I> <JMS> Loading destinations
Fri Mar 09 10:39:10 PST 2001:<I> <JMS> Initializing durable subscribers
Fri Mar 09 10:39:10 PST 2001:<I> <JMS> Recovering unstable messages
Fri Mar 09 10:39:10 PST 2001:<I> <JMS> Unstable message recovery
complete
Fri Mar 09 10:39:10 PST 2001:<I> <JMS> Initialization from backing
store complete
Fri Mar 09 10:39:10 PST 2001:<I> <JMS> Initializing from weblogic.properties
Fri Mar 09 10:39:10 PST 2001:<I> <JMS> java.sql.SQLException: Line


2: FOR UPDATE
clause allowed only for DECLARE CURSOR. Severity 15, State 2,
Procedure 'BRONCO null', Line 2 at weblogic.jdbcbase.mssqlserver4.TdsStatement.processWarning(Unknown
Source)
at weblogic.jdbcbase.mssqlserver4.TdsStatement.parseMsWarning

..........


Thanks a lot,
Madhu

Don Martin

unread,
Mar 13, 2001, 6:49:51 AM3/13/01
to

Madhu,

Are you sure that "server=bronco" is correct?
I'm not sure what "rel6_0@localhost" really
represents, but you might try:

url=jdbc:weblogic:mssqlserver4:localhost:1433
props=user=mnarasa;password=;server=rel6_0@localhost:1433

Either that or switch both localhost values to bronco,
depending on your DB configuration. While it's
likely not a prerequisite, I've always seen these
values the same.

Hope this helps,
Don


Madhu wrote:

> ...........

Balaji Venkataraman

unread,
Mar 13, 2001, 11:52:25 AM3/13/01
to
try this :

weblogic.jdbc.connectionPool.jmsPool=\
url=jdbc:weblogic:mssqlserver4,\
driver=weblogic.jdbc.mssqlserver4.Driver,\
initialCapacity=1,\
maxCapacity=5,\
capacityIncrement=2,\
props=user=mnarasa;password=;server=rel6_0@bronco:1433

Balaji.

"Madhu" <mna...@extensity.com> wrote in message
news:3aa92526$1...@newsgroups.bea.com...

0 new messages