JDBC 2.0 method not implemented error using bea jDriver for MS-SQLServer 2000
I'm trying to reconfigure WebLogic Portal 7.0 (Platform 7.0 SP2) to run on MS SQLServer
2000. According to the supported platform docs, the MS JDBC driver is not supported
by Portal, hence I'm using the BEA jDriver for SQLServer.
I'm now getting the following error when starting up Weblogic Portal which requires
a re-sync with the EBCC before the applications will work.
<28-Aug-03 09:28:30 BST> <Error> <Data Synchronization> <000000> <Application:
portalApp; Corrupted data encountered in the persistent store; PLEASE RE-SYNCHRONIZE
YOUR APPLICATION DATA WITH MODE "refresh-from-client" BEFORE CONTINUING! Failure
to do so may result in incomplete or otherwise corrupted server state.
Exception[com.bea.p13n.management.data.repository.PersistenceException: Failed
to refresh JDBC Persistence Manager.] - with embedded exception: [java.sql.SQLException:
java.sql.SQLException: This JDBC 2.0 method is not implemented] at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:506)
Has anyone else come across this problem and know how to resolve it. I have tried
using the MS JDBC Driver on the off chance that it would work, but this also produced
SQL Exceptions with the persistance store and would not work at all even after
syncing with the EBCC
Jim,
Thanks, I'm awaiting for my account to be enabled with customer contract support.
When this is done I will raise a case and send files as requested.
In the mean time it's worth noting that these settings have been made. Connection
to the DB is fine, the createDB, loadads, loaddocs and sync etc all worked fine.
The problem only exists when restarting the server and the portal persistance
store is trying to be refereshed. Once EBCC is re-synced all the DB access works
fine.
Steve
Jim Litton <reply@newsgroup> wrote:
Please open a support case and send in your set-environment.bat,
db_settings.properties, and config.xml from your domain directory after
trying the following.
Given that your operating system is Windows for performing all database
operations like create_db, loaddocs, sync. (because you should not
bother trying to run them on with UNIX).
Restore your set-environment.bat to it's original state. It does not
need to be touched.
Uncomment the MSSQL section in db_settings.properties.
database=MSSQL
db_version=2000
jdbcdriver=weblogic.jdbc.mssqlserver4.Driver
server=@MSSQL_SERVER@
port=@MSSQL_PORT@
dblogin=@MSSQL_USER@
dbpassword=@MSSQL_PASSWORD@
connection=jdbc:weblogic:mssqlserver4:@MSSQL_SERVER@:@MSSQL_PORT@
The dataSyncPool entry in config.xml should appear as:
<JDBCConnectionPool
Name="dataSyncPool"
DriverName="weblogic.jdbc.mssqlserver4.Driver"
URL="jdbc:weblogic:mssqlserver4:@MSSQL_SERVER@:@MSSQL_PORT@"
Properties="user=@MSSQL_USER@;password=@MSSQL_PASSWORD@"
Password="@MSSQL_PASSWORD@"
InitialCapacity="1"
MaxCapacity="5"
CapacityIncrement="1"
RefreshMinutes="99999"
ShrinkingEnabled="false"
Targets="sampleportalServer"
TestConnectionsOnReserve="false"
TestTableName="WEBLOGIC_IS_ALIVE"
/>
-- Jim
Similar Messages
-
JDBC 2.0 method not supported Error occuring in WL 6.1 sp1
Hi ,
When I connect to a mssqlserver 2000 using a session bean and execute the following
statement
"stmDataAccess=conDataAccess.createStatement(ResultSet.CONCUR_UPDATABLE,ResultSet.TYPE_SCROLL_INSENSITIVE);"
i get the following error at the client and server side
what can be wrong?.Support for Jdbc 2.0 is inherent in WL 6.1 isn't it?
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
Start server side stack trace:
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>Hi
As I know, not all mehtods are supported by WebLogic. For Example for Oracle only
a SubSet of the JDBC methods are supported (see the link http://e-docs.bea.com/wls/docs61///////oracle/API_joci.html#1070961).
I can imagine that for Microsoft Products this is even worse.
Regards Patrick
"Thomas" <[email protected]> wrote:
>
Hi,
I'm using the driver that comes along with the application server ie
weblogic.jdbc.mssqlserver4.Driver.If
this driver doesn't support JDBC 2.0 where can i find a suitable driver
as my
app needs updatable recordsets with updateXXX methods and absolute moves?
Thanks in advance
"noone_home" <[email protected]> wrote:
Hi,
It looks like your JDBC driver does not support JDBC 2.0. I believethe
the JDBC
driver for SQL Server that came with WLS 6.x supports only JDBC 1.1.
I'm making
the assumption that that is the driver which you are using.
hth.
"Thomas" <[email protected]> wrote:
Hi ,
When I connect to a mssqlserver 2000 using a session bean and execute
the following
statement
"stmDataAccess=conDataAccess.createStatement(ResultSet.CONCUR_UPDATABLE,ResultSet.TYPE_SCROLL_INSENSITIVE);"
i get the following error at the client and server side
what can be wrong?.Support for Jdbc 2.0 is inherent in WL 6.1 isn't
it?
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
Start server side stack trace:
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is
not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented>>> >>>Start server side stack trace:>>>java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method>is>>>not implemented>>> at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)>>> at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)>>> at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)>>> at java.lang.reflect.Method.invoke(Native Method)>>> at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)>>> at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)>>> at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown>>>Source)>>> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)>>> at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)>>> at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)>>> at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)>>> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)>>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)>>>End server side stack trace>>>
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
not implemented
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
not implemented
at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is>>>not implemented>>> >>>Start server side stack trace:>>>java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method>is>>>not implemented>>> at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)>>> at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)>>> at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)>>> at java.lang.reflect.Method.invoke(Native Method)>>> at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)>>> at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)>>> at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)>>> at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown>>>Source)>>> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)>>> at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)>>> at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)>>> at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)>>> at weblogic.kernel.ExecuteThread.execute>>(ExecuteThread.java:139)>>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)>>>End server side stack trace>>>
<<no stack trace available>> -
Cure for "501 Method Not Implemented" error at site in Firefox but not Chrome or IE?
I am receiving a "501 Method Not Implemented" error message at a site in Firefox but not in Chrome or IE. How can this be cured?
Do you get that error if you access the site or if you click a link to got to another page?
You can reload the page and bypass the cache with:
* Press and hold Shift and left-click the Reload button.
* Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
* Press "Cmd + Shift + R" (MAC)
See [[Keyboard shortcuts]] and [[Mouse shortcuts]]
* "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
* "Remove the Cookies" from sites that cause problems: Tools > Options > Privacy > Cookies: "Show Cookies"
Start Firefox in [[Safe Mode]] to check if one of your add-ons is causing your problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
* Don't make any changes on the Safe mode start window.
See [[Troubleshooting extensions and themes]] and [[Troubleshooting plugins]] -
Startworkflow : method not implemented error
Hi,
I am using the following code to run a stored procedure. But every time the stored procedure is called, I get a message that the Startworkflow method is not implemented. But still the procedure is called and everything works fine. Can you please provide
a solution to solve the error
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.MasterDataServices.WorkflowTypeExtender;
using System.Data.SqlClient;
using System.IO;
using System.Xml;
namespace MDSWorkflowExtender
public class MDSWorkflowExtender : IWorkflowTypeExtender
public void StartWorkflow(string workflowType, System.Xml.XmlElement dataElement)
// Open a connection on the workflow database.
SqlConnection workflowConn = new SqlConnection(@"Data Source=.; Database=DWH; Integrated Security=True");
// Create a command to call the stored procedure that adds a new user to the workflow database.
SqlCommand executeCommand = new SqlCommand("dbo.xxxxx", workflowConn);
// Execute the command.
workflowConn.Open();
executeCommand.ExecuteNonQuery();
workflowConn.Close();
throw new NotImplementedException();
workflowConn.Close();
// throw new NotImplementedException();
Remove the "throw new NotImplementedException();" statement in your code as I have shown by commenting
it out above. That statement probably is a left-over from the template. -
FUNCTION NOT IMPLEMENTED error when calling C# method from SAP, why?
Hi,
I've build a server stub in order to get SAP calling my own methods that exist in the C# world, for that I developed several methods in a class that extends SAPServer and then implemented them...
I added the special custom properties needed (Abap Name, length, etc) to the function and to its parameters, I've made the ABAP code required to call it...
I've checked, every parameters that I place in ABAP (importing, exporting and tables) are also defined in C# (its 53 parameters) with the same name (in C# they are in capital letters and in a diferent order but I tried this before and it didn't matter)...
The name of the function is the same...
How can I get the 'FUNCTION NOT IMPLEMENT' error in SAP?
What's going wrong when I get this error?
Can anyone tell me?
Is there any place in this site that has a error description and possible reasons?
When I get a parameter wrong I get a different error (I tried to make smaller functions and they work fine).
Thanks for the help,
Nuno Felino
Message was edited by: Nuno FelinoHi,
I'll explain what I'm doing:
- we have a set of services made in a C and VB that are available using an API in C#, these services must be available to SAP. So I have a program that will see what parameters the API service requires and makes a proxy so that SAP can call these services.
To do this I must map SAP types with C#, build the function signature and then implement it. So I cannot use the wizard to do this
Now, back to the question, what kind of customer attributes I got wrong to get that exception? The most logic is the AbapName of the function but they are equal (the one called in SAP and the one in the customer attributes of the function)...
Thanks for the answer, can you give me any more hint? -
Error when sending message: Method not implemented
Hi, All:
We have newly setup system and when we test sending test message from RWB, (RWB-Component Monitoring-Integration Engine-Test Tab), we got following error:
"Error when sending message: Method not implemented", I know this is related to post configuration issue, I just know someone has come cross the situation and how it was resolved.
Thanks
LiangHI Liang
Yes it looks like post installation problem. I have not come across this but i think you should check with the RFC created for IE while installation. To connect IE & AE and even the exchange profile if something is missing
Thanks
Gaurav -
Cannot create application - 405 Method Not Allowed error
Installed 11.1.2.1. Tried using EPMA to deploy app. Getting abort with the Method Not Allowed Error. Tried using Classic and getting the same error. Some of the details says "Server Error in Application "DEFAULT WEB SITE/HFM", "The page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used." Any thoughts on possible causes?
Hi Fsotto,
The below document would resolve the issue.
New Install on IIS 7, Cannot Access HFM from Workspace 404.3 Error in IIS Logs on HFM Web Server (Doc ID 1285684.1)
Hope this helps,
Please feel free to mark the answer as Helpful Answer/ Correct Answer should you find the relevant posting helpful so that it also helps us in keeping track of the answered queries.
Thank you,
Charles Babu J -
Hot code replace failed - Delete method not implemented
I debug my Java application with Eclipse (3.1). When I change my code during debugging, I get the following error message:
...MyApp at localhost:4540 (may be out of synch) was unable to replace the running code with the code in the workspace.
Reason:
Hot code replace failed - Delete method not implemented
What does that mean and how can I fix this?This means you changed a class while it was debugging an application and it could not update the class for the application while it was running.
The error suggests you may be running an older JVM, i.e. pre-1.4.2 but this error can occur with any JVM if the change is incompatible with the previous version of the class.
The hot replace often does not work for non trivial changes to code. -
Hi,
In our portal some users are getting 501 not implemented errors in some front pages.After refreshing everything works fine.Any body have any idea?How this can be solved?
Regards
ImranHI
Error Message:
Error 501/505: Not implemented or not supported.
Translation:
This error may occur when using Internet Explorer in Windows XP to view a Web page. This error can be caused by either having the HTTP 1.1 setting enabled or by an interference with Internet Explorer by a third-party product. Since there are some Web sites that still use HTTP 1.0, connection issues can arise if you have HTTP 1.1 enabled.
Solution:
The easiest fix for this error can be found if HTTP 1.1 is enabled. To fix the problem, simply disable HTTP 1.1. You can do this by clicking Tools in Internet Explorer and going to the Internet Options menu. Go to the Advanced tab and uncheck the box next to Use HTTP 1.1. Click OK and test to see if the issue is resolved. If you have resolved the issue, do not proceed with the following steps. If the error still remains, go back to the Tools menu in Internet Explorer and select Internet Options. Next, click the Advanced tab and check the box next to u201CShow friendly HTTP error messagesu201D and click OK. The next time this error occurs, a more detailed error message should appear to tell you which program is interfering with the proper display of the Web page. The more friendly error message will say something to the effect of, u201CHTTP version not supported by program name,u201D where program name is the name of the program that is preventing the Web page from displaying correctly. You can either remove this program to attempt to solve the problem or you can contact the manufacturer of the program to see if there is a fix available.
Regards,
vijay. -
Intermittent 501 Not Implemented Errors
Just wanted to ask if anyone else had come across intermittent Error 501 -- Not Implemented Errors while using PeopleTools 8.51? We are using PeopleTools 8.51.02 and have come across this a few times in both campus solutions and financials (same tools versions).
Any ideas or suggestions on what might be causing it? Signs tend to suggest and AJAX related problem.PeopleSoft has also published this resolution on My Oracle Support (MOS) - E-PIA: PeopleTools 8.50 and 8.51 - Intermittent "Error 501--Not implemented" Messages when Navigating to a Page Using IE7 or IE8 Browser. Doc ID : 1337266.1
-
I try to go to a certain website and get "Method not implemented"
I try and bring up Bluelight.ru and get a Method not implemented instead.I tried deleting cookies and it worked for a few days.I tried deleting cookies again but it didn't help.I called comcast and they said it was Mozilla.
It might have something to do with Proxies. Have a look in System Preferences>Network, click on your network - either ethernet or wifi - and click on the Proxies tab. Anything selected in there. If so deselect and then try.
Have you tried using another brrowser, maybe Chrome or Firefox? -
WLI-Core:489214: jpd not found error on bea weblogic 8.1 sp4
Hi,
I am developing a website using BEA Workshow 8.1 SP4 deployed on Integration single managed server cluster domain. I have some stateless jpd to process the stuff in asynchronized mode.
one in a week I am geting the following error:
[WLI-Core:489214]ProcessControl invocation failed[Service at /easWeb/com/pfizer/eas/marketing/processes/CreateDocCopies.jpd not found]
caused by: : com.bea.wlw.runtime.core.dispatcher.ServiceHandleException: Service at /easWeb/com/pfizer/eas/marketing/processes/CreateDocCopies.jpd not found
If I restart the managed server then this problem is resolved.
How can I fix this problem. Everything like queues, jsm server, connection pool is configured properly.
I can provide info about domain configuration if somebody needs.
Thanks,
UtkarshHello
I'm getting the same error using BEA Workshop 8.1 SP6. Could you resolve this issue?
please answer me by email. [email protected]
Thank you
Leandro -
Error When Trying to POST: Method not implemented in data provider class
Hi Experts,
I have created an Odata Service using Netweaver Gateway Service builder. I am using Advanced Rest Client to test the service. I can successfully GET my data, but I run into issues when I try and POST new data.
When trying to POST, I used the GET method to get the x-csrf-token, and added it to my header. I also updated the body XML with the data that I would like to POST. However, after sending the POST request, I am getting a "500 Internal Service Error" with the xml message "Method '<OdataServiceName>'_CREATE_ENTITY" not implemented in data provider class".
Any help on this would be greatly appreciated. Thanks!Hi Kelly,
Can you share screenshots of the error? Maybe something wrong with payload :can you share the same also? Did you try to debug it by putting a breakpoint in the CREATE_ENTITY method in the backend? Any luck?
Regards,
JK -
Getting "Method 'sign_in' does not exist" Error (using Charles)
This may be a bit off the FLEX field, and have to do with Zend Framework's ZEND_AMF class. Unfortunately I haven't been able to dig anything up, and comments posted on Wade Arnolds site have not received any responses, so I thought I'd give it a go here.
My ServiceController Class:
public function loginAction()
$this->_helper->viewRenderer->setNoRender();
$server = new Zend_Amf_Server();
$server->setClass('LoginAmfService', 'LoginService');
$server->setClassMap('CurrentUserVO', 'CurrentUserVO');
$server->setProduction(false);
print($server->handle());
My LoginAmfService class:
class LoginAmfService
* Main login function.
* @param string $name
* @param string $password
* @return CurrentUserVO
public function sign_in($name, $password)
$authAdapter = new Zend_Auth_Adapter_DbTable(Zend_Registry::get('db'), 'users', 'user_name', 'password', 'PASSWORD(?) AND active = 1');
$returnValue = new CurrentUserVO();
$authAdapter->setIdentity(htmlspecialchars($name))
->setCredential(htmlspecialchars($password));
$authResult = $authAdapter->authenticate();
if ($authResult->isValid())
$userArray = $authAdapter->getResultRowObject(array('id', 'first_name', 'last_name', 'title', 'photo'));
$returnValue->first_name = $userArray->first_name;
$returnValue->last_name = $userArray->last_name;
$returnValue->title = $userArray->title;
$returnValue->photo = $userArray->photo;
$returnValue->token = $userArray->id;
return $returnValue;
* Function used to log people off.
public function sign_out()
$authAdapter = Zend_Auth::getInstance();
$authAdapter->clearIdentity();
My SignIn FLEX module (the relevant portions):
<mx:RemoteObject
id="LoginRemote"
destination="login"
source="SignIn"
showBusyCursor="true"
fault="parentDocument.handleFault(event)"
>
<mx:method name="sign_in" result="signin_handle(event)" />
<mx:method name="sign_out" result="signout_handle(event)" />
</mx:RemoteObject>
<mx:Script>
<![CDATA[
import mx.rpc.events.FaultEvent;
import mx.utils.ArrayUtil;
import mx.rpc.events.ResultEvent;
import mx.controls.Alert;
import com.brassworks.ValueObjects.CurrentUserVO;
import mx.events.VideoEvent;
[Bindable]
private var this_user:CurrentUserVO = new CurrentUserVO();
private function mdl_init():void
focusManager.setFocus(txt_username);
private function signin_handle(event:ResultEvent):void
this_user = event.result as CurrentUserVO;
if (this_user.token == null) {Alert.show("Supplied login credentials are not valid. Please try again.");}
else
this.parentApplication.setUser(this.this_user);
private function signout_handle(event:ResultEvent):void
private function sign_in(event:Event):void
try
//Alert.show(txt_name.text + "|" + txt_password.text);
LoginRemote.sign_in(txt_username.text, txt_password.text);
catch (error:Error)
this.parentDocument.handleFault(error);
private function sign_out(event:Event):void
private function show_error(error:Error, s_function:String):void
Alert.show("Method:" + s_function + "\nName: " + error.name + "\nID: " + error.errorID + "\nMessage: " + error.message + "\nStack Trace: " + error.getStackTrace() + "\nError: " + error.toString());
private function handleFault(event:FaultEvent):void
Alert.show(event.fault.faultDetail, event.fault.faultString);
]]>
</mx:Script>
Now, all this is great and good, as it works with Zend Framework 1.7.6. However, when I try to upgrade to 1.7.8 (to take advantage of session management and other bug-fixes), I get the following error (using Charles):
#1 /var/web/htdocs/core/library/Zend/Amf/Server.php(390): Zend_Amf_Server->_handle(Object(Zend_Amf_Request_Http))
#2 /var/web/htdocs/core/application/default/controllers/ServicesController.php(73): Zend_Amf_Server->handle()
#3 /var/web/htdocs/core/library/Zend/Controller/Action.php(503): ServicesController->loginAction()
#4 /var/web/htdocs/core/library/Zend/Controller/Dispatcher/Standard.php(285): Zend_Controller_Action->dispatch('loginAction')
#5 /var/web/htdocs/core/library/Zend/Controller/Front.php(934): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#6 /var/web/htdocs/core/application/bootstrap.php(39): Zend_Controller_Front->dispatch()
#7 /var/web/htdocs/core/public/index.php(5): Bootstrap->runApp()
#8 {main} ?Method "sign_in" does not exist
I have no idea why this would not work anymore. My assumption is that I am not correctly setting up Zend_Amf (but then again, my counter-argument is that it worked before, so ..... ????)
Thanks for any help!
-MikeFor those that are also fighting this issue:
The problem appears to be that the RemoteObject needs to specify the class containing the methods as a source parameter. According to this bug report (http://framework.zend.com/issues/browse/ZF-5168) it is supposed to have been addressed, but apparently has re-emerged in Zend_Amf since version 1.7.7.
Using my example above, I would have to specify the RO as:
<mx:RemoteObject
id="LoginRemote"
destination="login"
source="LoginAmfService"
showBusyCursor="true"
fault="parentDocument.handleFault(event)"
>
<mx:method name="sign_in" result="signin_handle(event)" />
<mx:method name="sign_out" result="signout_handle(event)" />
</mx:RemoteObjecct> -
405 Method Not Allowed error from images directory
Some background: I'm implementing fusioncharts in APEX and the commercial version comes with an Save as Image capability. When the user wants to save the chart as an image, an aspx file is called which calls a POST method to the directory where the aspx file is located.
I store the aspx and its dependent files in a subfolder in the images directory and reference it using http://myserver/i/imagesaving/FusionChartsSave.aspx. Then when I try to save, I get 405 Method Not Allowed: 'the requested method POST is not allowed for the URL /i/imagesaving/FusionChartsSave.aspx.'
The aspx functions work for sure because I am able to successfully save to image when I put the files in IIS and reference the url to the aspx file that way.
My main concern is trying to keep all the files in the APEX environment which is Apache. Is there a place where I can perform the POST or configure apache to a directory that allows POST?
thanks!Hi,
I am facing the same error, patch upgraded from 12 to 18.
URL iview was working on patch 12 , but after upgrade , one particular URL iview is not working.
Preview works fine, if I paste the URL in a new window it workf fine,
but when I try to access as an end user , the following error is faced
"HTTP Error 405 - The HTTP verb used to access this page is not allowed.
Internet Information Services (IIS)".
I have tried to use "Open in new Window" property, but it dint help.
Can anybody suggest.??
Thanks in anticipation,
Juhi
Maybe you are looking for
-
I created a family sharing network consisting of my me, my wife, and my 16 y/o son. I can see/download my wife's purchases and she can see/download my purchases. I can also see/download my sons purchases. My son can see my purchases, but when he at
-
Transaction/Movement type on the vendor line item
When we post to a vendor using F-43 (or FB01) using posting key 31. We want the field Transaction type to be available for input in the vendor line item. But this is not happening. note: In the FSG of vendor recon account and Posting key 31 this fiel
-
APIs for achieving CJ9BS "Copy Planning" transaction.
Hello, I have to achieve the functionality of CJ9BS "Copy Planning" from version 0 to version 2. I can achieve this by using CJ9BS transaction. Would you guys know of an API that can do the same. Thanks for all your help. Best Regards Sumit.
-
Boot Camp installer updates crashing WinXP
Hello I installed WinXP on my iMac today (2.6Ghz i5 processor, 16GB RAM, 2TB drive, OSX 10.6.8). After running Windows (all the updates were installed), I tried to update the Boot Camp. My OSX disc installs Boot Camp 3.0 and I Software Updater is not
-
HOW DO I FIX THIS PROBLEM: E_ACT_NOT_READY ?