ORA 1461 exception when settting up JMS to use jdbc store
Andreas
When trying to set up a JMS server to use a jdbc store we get an exception with an
ORA 01461 error - "can bind a LONG value only for insert into a LONG column". The
tables are created in the database but then the exception occurr.
We are using
- weblogic 6.1 sp2
- Oracle client 9.0.1
- Sun Solaris 8
- weblogics jDriver that came with the distribution
When changing to use a connection pool set up with oracles thin driver we get an
ORA 0600 general exception instead.
Excerpt from config file:
<JMSServer Name="EBP JMS Server" Store="EBP JMS JDBC Store" Targets=""><JMSQueue
JNDIName="testQueue" Name="testQueue"/>
</JMSServer>
<JMSJDBCStore ConnectionPool="EBPDEV"
Name="EBP JMS JDBC Store" PrefixName="EBP"/>
<JDBCConnectionPool DriverName="weblogic.jdbc.oci.Driver"
MaxCapacity="10" Name="EBPDEV"
Properties="user=ebp;password=ebp;server=EBPDEV"
Targets="ebpServer" URL="jdbc:weblogic:oracle"/>
Anyone have a solution to the problem?
/ Andreas
Tom Barnes
Meanwhile you might want to give the 8.1.7 client a shot.
Varun Garg
I used to have a slightly differnt problem, I have configured my store on file system
rather than JDBC to take care of that. Basically what used to happen is that after
a while the connection to the store would be lost and it would thorw an exception
to the client that there was a problem writing to the store.
Since I configured to a file store its working fine.
Varun
Stephen Felts
the JDBC connection pool, add the attribute
PreparedStatementCacheSize="0"
We have seen some new problems with Oracle 9.0.1 regarding reusing prepared
statements that have null values one time, then a long integer value the
next time.
This will turn off the statement cache so you can't run into this problem.
Thanks.
"Andreas " <andrea...@hi3gaccess.se> wrote in message
news:3cd0f201$1...@newsgroups2.bea.com...
Andreas
I tried this and unfortunately it didn't help.
/ Andreas
Andreas
Here is the stacktrace when using jDriver
/ Andreas
<May 3, 2002 10:36:04 AM CEST> <Alert> <JMS> <JMSServer "EBP JMS Server", store failed
to open, java.io.IOException: JMS JDBC store, connection pool = <EBPDEV>, prefix
= <EBP>: change state
java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG
column
at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:240)
at weblogic.jdbc.oci.Statement.executeUpdate(Statement.java:990)
at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
at weblogic.jms.store.JDBCIOStream.changeState(JDBCIOStream.java:417)
at weblogic.jms.store.JDBCIOStream.setVersion(JDBCIOStream.java:1592)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:290)
at weblogic.jms.store.JMSStore.open(JMSStore.java:107)
at weblogic.jms.backend.BEStore.open(BEStore.java:180)
at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:390)
at weblogic.jms.JMSService.createBackEnd(JMSService.java:907)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:1274)
at weblogic.jms.JMSService.addDeployment(JMSService.java:1170)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
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.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
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 $Proxy17.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at weblogic.management.console.webapp._domain.__jmsserver$TargetAttribute.doSet(__jmsserver.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Tom Barnes
Date: Fri, 03 May 2002 15:28:19 -0400
From: Tom Barnes <ple...@replyinnewsgroup.com>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: weblogic.developer.interest.jms
To: Andreas <andrea...@hi3gaccess.se>
Subject: Re: ORA 1461 exception when settting up JMS to use jdbc store
References: <3cd0f201$1...@newsgroups2.bea.com> <3CD12CD0...@replyinnewsgroup.com> <3cd24d5d$1...@newsgroups2.bea.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 63.96.180.215
X-Original-NNTP-Posting-Host: 63.96.180.215
X-Trace: 3 May 2002 12:28:21 -0700, 63.96.180.215
X-Original-Trace: 3 May 2002 12:28:21 -0700, 63.96.180.215
Organization: BEA SYSTEMS Inc
Lines: 70
XPident: Unknown
Path: newsgroups2.bea.com
Xref: newsgroups2.bea.com weblogic.developer.interest.jms:9052
This is a new one. Other than trying different drivers at different versions (which you have done), I have
no suggestion beyond dropping the tables before trying each new driver (which you might not have done).
A hack solution might be to modify the .ddl that creates the tables to change the column types from int to long,
and run the ddl yourself (JMS doc appendix tells how to extract the .ddl file from the weblogic.jar and run it).
Meanwhile, I suggest using a file store instead of a JDBC store for the duration, and contacting customer support.
Tom
Rajesh Mirchandani
Date: Mon, 06 May 2002 11:08:09 -0700
From: Rajesh Mirchandani <Re...@ToNewsgroup.Only>
Reply-To: Re...@ToNewsgroup.Only
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: weblogic.developer.interest.jms
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: 65.193.194.6
X-Trace: 6 May 2002 11:11:43 -0700, 65.193.194.6
X-Original-Trace: 6 May 2002 11:11:43 -0700, 65.193.194.6
Organization: BEA SYSTEMS Inc
Lines: 64
XPident: Unknown
Path: newsgroups2.bea.com
Xref: newsgroups2.bea.com weblogic.developer.interest.jms:9058
Try setting the NLS_LANG(same as the db) value in the startup script.
Andreas wrote:
--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support