Error: Element type "stateful-session-descriptor" must be declared ?

Hi,
while running the ant i am getting this error.
jar_ejb:
[jar] Building jar: D:\bdms\src\ejbdist\std_ejb_bdms_eapm.jar
ejbc:
[java]
[java] ERROR: ejbc found errors while parsing the descriptor for src/ejbdis
t/std_ejb_bdms_eapm.jar:
[java]
[java]
[java]
[java] ERROR: Error from ejbc: Error parsing file 'META-INF/weblogic-ejb-ja
r.xml' at line: 394 column: 55. Element type "stateful-session-descriptor" must
be declared.
[java]
[java]
[java] ERROR: ejbc couldn't load descriptor from jar
[java]
[java] Java Result: 1
Here with i have included the ejb-jar.xml & weblogic-ejb-jar.xml lines. I am using a service locator to call the ejb. please help me.
ejb-jar.xml
<session>
<ejb-name>ValueListHandlerEJB</ejb-name>
<home>com.pagination.ValueListHandlerEJBHome</home>
<remote>com.pagination.ValueListHandlerEJBRemote</remote>
<ejb-class>com.pagination.ValueListHandlerEJB</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
<resource-ref>
     <res-ref-name>jdbc/DataSource</res-ref-name>
     <res-type>javax.sql.DataSource</res-type>
     <res-auth>Container</res-auth>
</resource-ref>
     </session>
weblogic-ejb-jar.xml
<weblogic-enterprise-bean>
<ejb-name>ValueListHandlerEJB</ejb-name>
<stateful-session-descriptor>
<stateful-session-cache>
     <max-beans-in-cache>100</max-beans-in-cache>
     <idle-timeout-seconds>600</idle-timeout-seconds>
</stateful-session-cache>
</stateful-session-descriptor>
     <reference-descriptor>
<resource-description>
          <res-ref-name>
jdbc/DataSource
</res-ref-name>
     <jndi-name>
adslDataSource
</jndi-name>
</resource-description>
     </reference-descriptor>
     <enable-call-by-reference>True</enable-call-by-reference>
     <jndi-name>ValueListHandlerEJB</jndi-name>
</weblogic-enterprise-bean>

but a bean's deployment descriptor lies in the
meta-inf folder, right?Sorry, my mistake. I was thinking of WAR files while writing. Thanks for pointing out.
Regards,
$ Carol.

Similar Messages

"caching-descriptor" must be declared error when using ejbc on WLS6.0 with EJB 1.1

I'm compiling with ejbc an entity bean .jar. Using WLS 6.0. In the ejb-jar.xml,
I've set version to EJB 1.1. I've made sure the weblogic-ejb-jar.xml has the caching-descriptor
element defined (used to work with WLS 5.1).
Thanks.
Sayid
Error is : org.xml.sax.SAXParseException: Element type "caching-descriptor" must
be declare d. at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java
:1008) at weblogic.apache.xerces.validators.common.XMLValidator.reportRecoverab
leXMLError(XMLValidator.java:1236) at weblogic.apache.xerces.validators.common.XMLValidator.validateElement
AndAttributes(XMLValidator.java:2673) at weblogic.apache.xerces.validators.common.XMLValidator.callStartElemen
t(XMLValidator.java:818) at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher
.dispatch(XMLDocumentScanner.java:1222) at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
mentScanner.java:380) at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:128 ) at
weblogic.ejb20.dd.xml.WebLogicEjbJarLoader_WLS600.process(WebLogicEjb JarLoader_WLS600.java:455)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:9 3) at
weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:4 7) at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:3
8) at weblogic.ejbc20.runBody(ejbc20.java:665) at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.ejbc.main(ejbc.java:20) --------------- nested within: ------------------
weblogic.xml.process.XMLParsingException: Element type "caching-descriptor" must
be declared. - with nested exception: [org.xml.sax.SAXParseException: Element
type "caching-descriptor" must be declar ed.] Line: 8 Column: 27 at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:132
) at weblogic.ejb20.dd.xml.WebLogicEjbJarLoader_WLS600.process(WebLogicEjb JarLoader_WLS600.java:455)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:9 3) at
weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:4 7) at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:3
8) at weblogic.ejbc20.runBody(ejbc20.java:665) at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.ejbc.main(ejbc.java:20) ERROR: weblogic.xml.process.XMLParsingException:
Element type "caching-descripto r" must be declared. - with nested exception:
[org.xml.sax.SAXParseException: Element type "caching-descriptor" must be declar
ed.] Line: 8 Column: 27

but a bean's deployment descriptor lies in the
meta-inf folder, right?Sorry, my mistake. I was thinking of WAR files while writing. Thanks for pointing out.
Regards,
$ Carol.

Deploy Error when using Stateful Session Bean inside Webdynpro

Hi,
I'm trying to create a webdynpro project that uses a stateful session bean
I have created DC's for a EJB Module project, Enterprise Application and Webdynpro component. Created the bean, built it, added it's package to the public part, added the EJB Module to the EAR project. Built the EAR project. Added the EJB Module project and Enterprise Application project as a used DC in the Webdynpro DC.
In the Webdynpro DC I added com.sap.archive-packaging.default.update-descriptors=true in the build.properties file of the cfg directory. (using the navigator view) That resolved an error while building it.
Deployed the Enterprise Application DC without problems.
Tried to deploy the Webdynpro DC but I get the following error:
Jun 16, 2008 9:40:46 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] WARNING:
[012]Deployment finished with warning
Settings
SDM host : 10.64.36.74
SDM port : 50018
URL to deploy : file:/C:/DOCUME~1/JESCHA~1/LOCALS~1/Temp/temp59822company.nl~projempactcmp.ear
Result
=> deployed with warning : file:/C:/DOCUME~1/JESCHA~1/LOCALS~1/Temp/temp59822company.nl~projempactcmp.ear
Finished with warnings: development component 'projempactcmp'/'company.nl'/'local'/'20080616094022':Caught exception during application startup from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while starting application company.nl/projempactcmp and wait. Reason: Clusterwide execption: server ID 6060950:<--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed implicit start for company.nl/projempejb : Unknown state(5)', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed implicit start for company.nl/projempejb : Unknown state(5)', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed implicit start for company.nl/projempejb : Unknown state(5)', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed implicit start for company.nl/projempejb : Unknown state(5) (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : Got problems during deployment
Does anyone know what this error means and how to resolve it. I searched the forum but only found errors that look like this relating to XI not to Webdynpro.......
Thansk,
Jeschael
Edited by: J.V. Lebbink on Jun 17, 2008 6:52 AM

Default is 30mts.
This is done as a parameter in orion-ejb-jar.xml. Please look at the EJB Guide at http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/a97677/dtdxml.htm#634197 for details
regards
Debu

Error While passivating Stateful session bean

I also have same problem when WL passivating. However, the exception throwing from
WL saying the "Ignoring exception raised while passivating".
My question is will that exception lead to failure of passivating and evenually
lead to memory leakage? I just thought that the memory is still in cache either
removed or passivated, as a result more and more memory will be used up as more
failure occurs.
Frank
Rob Woollen <[email protected]> wrote:
It looks like you have a reference to a DB Connection as a member
variable. This reference should be transient. You can re-acquire it
in
ejbActivate.
-- Rob
Hemant Arora wrote:
Hi
Can anybody please clarify the error that I'm getting while runningthe
stateful session bean with weblogic
I have instantiated 20 stateful session beans all using the DB connection
but if the connection is unaailable I'm making the beans to wait.
I'm not removeing the beans and again making the instance of 20 another
beans
The max beans in cache is 25.
Thanks
Hemant
This is the output at the console of the weblogic
ejbPassivate()
Tue Jul 17 20:58:00 GMT+05:30 2001:<I> <EJB JAR deployment
d:/weblogic/myserver/romanCount.jar> Ignoring exception raised while
passivating:
java.io.NotSerializableException:
weblogic.jdbc20.rmi.internal.ConnectionImpl
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com

Error while import into 10g --- 'DBMS_EXPORT_EXTENSION' must be declared

Hi,
We are in a process to upgrade our database from Oracle 8.1.7 to Oracle 10.2.0
We are upgrading our database and on the different machine.
Setup pre-requsities for 10g rel2 has been done.
And now I am import the data from the Export File (dump file).
I am importing data schema wise one by one using Database Control EM available in 10g.
Data of two schemas has been succesfully been imported.
Now when i am trying to import the data for third schema i am gettting the following errors as below.
Import parameters that i have used ::
FILE=E:\EXP_FULL_PAY.DMP
LOG=E:\IMPORT.LOG
FROMUSER=PAY02
TOUSER=PAY02
TABLES=SYSMST
GRANTS=y
INDEXES=y
ROWS=y
CONSTRAINTS=y
IGNORE=y
SKIP_UNUSABLE_INDEXES=y
DATAFILES=n
Error Details ::
Username:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V08.01.07 via conventional path
Warning: the objects were exported by HP, not by you
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
import server uses WE8ISO8859P1 character set (possible charset conversion)
export client uses WE8ISO8859P1 character set (possible charset conversion)
export server uses WE8ISO8859P1 NCHAR character set (possible ncharset conversion)
. importing PAY's objects into PAY
. . importing table "SYSMST" 2 rows imported
IMP-00058: ORACLE error 6550 encountered
ORA-06550: line 1, column 11:
PLS-00302: component 'DBMS_EXPORT_EXTENSION' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
IMP-00017: following statement failed with ORACLE error 6550:
"BEGIN SYS.DBMS_EXPORT_EXTENSION.SET_IMP_SKIP_INDEXES_OFF; END;"
IMP-00003: ORACLE error 6550 encountered
ORA-06550: line 1, column 12:
PLS-00302: component 'DBMS_EXPORT_EXTENSION' must be declared
ORA-06550: line 1, column 8:
PL/SQL: Statement ignored
IMP-00017: following statement failed with ORACLE error 6550:
"BEGIN SYS.DBMS_EXPORT_EXTENSION.SET_IMP_SKIP_INDEXES_OFF; END;"
IMP-00003: ORACLE error 6550 encountered
ORA-06550: line 1, column 12:
PLS-00302: component 'DBMS_EXPORT_EXTENSION' must be declared
ORA-06550: line 1, column 8:
PL/SQL: Statement ignored
IMP-00017: following statement failed with ORACLE error 6550:
"BEGIN SYS.DBMS_EXPORT_EXTENSION.SET_IMP_SKIP_INDEXES_OFF; END;"
IMP-00003: ORACLE error 6550 encountered
ORA-06550: line 1, column 12:
PLS-00302: component 'DBMS_EXPORT_EXTENSION' must be declared
ORA-06550: line 1, column 8:
PL/SQL: Statement ignored
IMP-00017: following statement failed with ORACLE error 6550:
"BEGIN SYS.DBMS_EXPORT_EXTENSION.SET_IMP_SKIP_INDEXES_OFF; END;"
This error goes into the infinite loop and at last shows the message as increase the flash recovery area size.
Kindly provide the guidance...
Regards

Hi Nichols,
As u have told that some reserved word must have been used as a database object name, but as i have also mentioned the name of table that is to be imported.
i.e. "SYSMST" which i think so, it cannot be a reserved word
Neither i can change the table name as it may generate further complications.
And also when i havae refresh the Database Control EM page I am getting the following error ::
Archiver is unable to archive a redo log because the output device is full or unavailable.
Agent Connection to Instance :
Status:: Failed
Details ORA-00257:: archiver error. Connect internal only, until freed. (DBD ERROR: OCISessionBegin
Kindly guide...
Regards
Milin
Message was edited by:
user640001

Cursor Error in trigger - Statement Ignored/identifier must be declared PLS

I have been asked to implement a trigger and believe I have the code complete but am getting a final error on the compile. I have been running in circles for a day trying to resolve my issue. I have no PL/SQL knowlege so have been pulling from a book and google. I have three Cursors defined and the third compiles fine, the first two give the below error though I can't see a significant difference between the three. I can't help but think it is something stupid I am not seeing but I am at a loss.
If I comment out the reference to the cursor it will compile with the cursor definition but as soon as I add the Open statement the errors below appear.
Any help would be greatly appreciated as my head is getting sore.
Thanks
Mike
Error(30,13): PL/SQL: Statement ignored
Error(30,20): PLS-00201: identifier 'CURSORGETFROMDISTMAKRERS' must be declared
Error(51,13): PL/SQL: Statement ignored
Error(51,20): PLS-00201: identifier 'CURSORGETTODISTMAKRERS' must be declared
-- Table I am writing to
create table IMSV7.CTRANSWODISTMARK (
WORKORDERKEY INTEGER,
DISTMARKFROM NUMBER (9,4),
DISTMARKFROMATTRIBUTE VARCHAR (10),
DISTMARKTO NUMBER (9,4),
DISTMARKTOATTRIBUTE VARCHAR (10)
-- Excerpt from the HISTORY table I am placing the trigger against
COMPKEY NUMBER (9,0)
DISTFROMFT FLOAT
DISTTOFT FLOAT
HISTKEY NUMBER (9,0)
-- Trigger code
CREATE OR REPLACE TRIGGER MaintainCTRANSWODISTMARK
AFTER INSERT or UPDATE of DISTFROMFT, DISTTOFT ON IMSV7.HISTORY
REFERENCING NEW as NewWO
FOR EACH ROW
BEGIN
DECLARE
-- Declare cursors
CURSOR CursorGetFromDistMarkers (WOCompKey IN NUMBER, WODistFromFT IN FLOAT) IS
SELECT ATTRCODE, DISTFROMFT, MARKERFROM from RWATTRDF DF, RWATTR A
where WOCompkey = A.COMPKEY AND DF.ATTRKEY = A.ATTRKEY and DF.ATTRTYPE = 'DISTMARK'
and WODistFromFT >= DISTFROMFT and WODistFromFT <= DISTTOFT
order by A.EFFDATE DESC, DISTFROMFT DESC;
FromDistanceMarker CursorGetFromDistMarkers%ROWTYPE;
CURSOR CursorGetToDistMarkers (WOCompKey IN NUMBER, WODistToFT IN FLOAT) IS
SELECT ATTRCODE, DISTFROMFT, MARKERFROM from RWATTRDF DF, RWATTR A
where WOCompkey = A.COMPKEY AND DF.ATTRKEY = A.ATTRKEY and DF.ATTRTYPE = 'DISTMARK'
and WODistToFT >= DISTFROMFT and WODistToFT <= DISTTOFT
order by A.EFFDATE DESC, DISTFROMFT DESC;
ToDistanceMarker CursorGetToDistMarkers%ROWTYPE;
CURSOR CursorGetCTRANSWODistMark (WOHistKey IN NUMBER) IS
SELECT WORKORDERKEY from CTRANSWODISTMARK
where WORKORDERKEY = WOHistKey;
CTRANSWODistMark CursorGetCTRANSWODistMark%ROWTYPE;
varDistmarkFrom NUMBER;
varDistmarkFromAttribute VARCHAR2(10);
varDistmarkTo NUMBER;
varDistmarkToAttribute VARCHAR2(10);
BEGIN
-- Process From measurement
IF NOT CursorGetFromDistMakrers%ISOPEN
THEN
OPEN CursorGetFromDistMarkers(:NewWO.COMPKEY, :NewWO.DISTFROMFT);
END IF;
FETCH CursorGetFromDistMarkers INTO FromDistanceMarker;
IF CursorGetFromDistMarkers%NOTFOUND
THEN
-- No distance markers found, use MILES
varDistmarkFrom := :NewWO.DISTFROMFT / 5280;
varDistmarkFromAttribute := 'MILES';
ELSE
-- Found a distance marker, convert to its units and use those
-- Distance is the Marker start distance plus the offset from that start of the marker
varDistmarkFrom := FromDistanceMarker.MARKERFROM + :NewWO.DISTFROMFT - FromDistanceMarker.DISTFROMFT;
varDistmarkFromAttribute := FromDistanceMarker.ATTRCODE;
END IF;
CLOSE CursorGetFromDistMarkers;
-- Process To measurement
IF NOT CursorGetToDistMakrers%ISOPEN
THEN
OPEN CursorGetToDistMarkers(:NewWO.COMPKEY, :NewWO.DISTTOFT);
END IF;
FETCH CursorGetToDistMarkers INTO ToDistanceMarker;
IF CursorGetToDistMarkers%NOTFOUND
THEN
-- No distance markers found, use MILES
varDistmarkTo := :NewWO.DISTTOFT / 5280;
varDistmarkToAttribute := 'MILES';
ELSE
-- Found a distance marker, convert to its units and use those
-- Distance is the Marker start distance plus the offset from that start of the marker
varDistmarkTo := ToDistanceMarker.MARKERFROM + :NewWO.DISTTOFT - ToDistanceMarker.DISTFROMFT;
varDistmarkToAttribute := ToDistanceMarker.ATTRCODE;
END IF;
CLOSE CursorGetToDistMarkers;
-- Check for existing record to know if we should add or update
IF NOT CursorGetCTRANSWODistMark%ISOPEN
THEN
OPEN CursorGetCTRANSWODistMark(:NewWO.HISTKEY);
END IF;
FETCH CursorGetCTRANSWODistMark INTO CTRANSWODistMark;
IF CursorGetCTRANSWODistMark%NOTFOUND
THEN
-- Record does not exist, add one
Insert into CTRANSWODISTMARK (WORKORDERKEY, DISTMARKFROM, DISTMARKFROMATTRIBUTE, DISTMARKTO, DISTMARKTOATTRIBUTE)
values (:NewWO.HISTKEY, varDistmarkFrom, varDistmarkFromAttribute, varDistmarkTo, varDistmarkToAttribute);
ELSE
-- Existing record, update it
Update CTRANSWODISTMARK set DISTMARKFROM = varDistmarkFrom, DISTMARKFROMATTRIBUTE = varDistmarkFromAttribute,
DISTMARKTO = varDistmarkTo, DISTMARKTOATTRIBUTE = varDistmarkToAttribute
Where WORKORDERKEY = :NewWO.HISTKEY;
END IF;
END;
END;
run;
show errors trigger MaintainCTRANSWODISTMARK;

the cursor is mispelled
IF NOT CursorGetFromDistMakrers%ISOPENchange it to:
IF NOT CursorGetFromDistMarkers%ISOPEN

Plz help!! idempotent methods stateful session beans? (failover)

          plz help!! idempotent methods stateful session beans? (failover)
          Hi there,
          Im trying to failover my shopping cart implemented using stateful ejb, the replication
          is working but the failover is not (Object not found exception....).
          By design is hard to think on an stateful ejb using idempotent methods, but after
          checking the documentation in detail im completely confused, so im starting to
          wonder if i should use idempotent methods or manual retry in case one server is
          down.
          Plz take a loo at these explanations about faiolver in the WLS edocs.
          "....With clustered objects, automatic failover generally occurs only in cases
          where the object is idempotent.....Because of this, replica-aware stubs will not,
          by default, attempt to retry a method that fails after the request is sent but
          before it returns. This behavior can be overridden by marking a service idempotent..."
          BUT
          "By default, a stateful session bean's Home stub provides load balancing and failover
          for its method invocations to any clustered server where the bean is deployed...."
          So is possible to achieve automatic failover (not only load balancing) for stateful
          ejb without having to worry about state-changes or manual retry. (i know the retry
          is requiered if the server crashed just before finishing a transaction but this
          is not what im talking about).
          Any help will be highly appreciated
          Alan


          Ryan,
          Yes, im deploying using In-memory replication and clusterable elements, when try
          to invoke the method (after one of the nodes is down) i recieve an "java.rmi.NoSuchObjectException:
          Bean has been deleted".
          I believe all this could be related to some sort of issue with JNDI Lookup in
          the cluster, but haavent been able to get a clue to make it work....(almost desesperate
          by now)
          Alan
          "ryan upton" <[email protected]> wrote:
          >Alan,
          >
          >If the state isn't maintained during failover I would suspect a
          >configuration error. Have you set the <replication-type> element within
          ><stateful-session-clustering> tag in the bean's deployment descriptor?
          >
          >"Alan" <[email protected]> wrote in message
          >news:40e17cf7$1@mktnews1...
          >>
          >> Ryan,
          >>
          >>
          >> Maybe i didnt explain myself, in the scenario im dealing with I KNOW
          >the
          >method
          >> finished succesfully (example, the user succesfully added an item to
          >a
          >cart).
          >>
          >>
          >> Just after that one of the nodes goes down, and the user decides to
          >add a
          >new
          >> item (new invocation , not a retry of failed one) on the same session.
          >>
          >> This is the case in which failover should work automatically as you
          >say,
          >meaning
          >> the new method invokation should be able to retrieve the session state
          >info from
          >> the replica and switch the primary.....Well, this is the part wich
          >isnt
          >working
          >> :( as i understand it should transparently
          >>
          >> I believe could be a config issue , but have no way to make it work.
          >>
          >> Regards,
          >>
          >> Alan
          >> "ryan upton" <[email protected]> wrote:
          >> >
          >> >"Alan" <[email protected]> wrote in message
          >news:40e06296@mktnews1...
          >> >>
          >> >> Ryan,
          >> >>
          >> >> Thanks for clearing the both conditions a bit more, in this case
          >my
          >> >issue
          >> >has
          >> >> to do with the scenario #1 in which subsequent calls (invocations)
          >> >go to a
          >> >node
          >> >> which isnt avaliable(down), do you have any idea of in what conditions
          >> >the
          >> >"automnatic"
          >> >> failover would fail??? (meaning why the stub would try to dispatch
          >> >a call
          >> >to the
          >> >> same previous node)
          >> >>
          >> >> Thanks for the help again
          >> >>
          >> >
          >> >Subsequent calls won't go to a node that's down. That's the whole
          >> >point
          >> >;-). Failover is always automatic, what you are getting confused
          >on
          >> >is
          >> >automatic method re-execution upon failover which happens if the method
          >> >has
          >> >been marked as idempotent. The logic is this: if I failover to an
          >EJB
          >> >that
          >> >I know is still alive, I can't safely call the same method again.
          > Why?
          >> >Because I don't know how much of the method completed the last time
          >before
          >> >the previous bean's failure. So if the bean can yield multiple results
          >> >from
          >> >multiple invocations I had better play it safe and not re-execute
          >the
          >> >method
          >> >on the bean I failed over to (unless it's idempotent because in that
          >> >case it
          >> >doesn't matter how many times I call it, it always does the same thing).
          >> > In
          >> >scenario #1 and #2 failover is automatic and all new calls are executed
          >> >against the bean the client failed over to, but only idempotent methods
          >> >are
          >> >re-executed.
          >> >
          >> >
          >>
          >
          >

Stateful Session Beans are not passivated / serialized when cache idle time

Technology: Sun Application Server version 7.0.0_01; JDK 1.4.1; developed on Windows 2000; Tested on Sun Solaris.
Initial error on Sun Solaris:
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr: Exception in thread "service-j2ee-25" org.omg.CORBA.OBJ_ADAPTER: vmcid: SUN minor code: 1015 completed: No
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.POA.GenericPOAServerSC.preinvoke(GenericPOAServerSC.java:389)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.POA.ServantCachePOAClientSC.initServant(ServantCachePOAClientSC.java:112)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.POA.ServantCachePOAClientSC.setOrb(ServantCachePOAClientSC.java:95)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.createDelegate(CDRInputStream_1_0.java:760)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.internalIORToObject(CDRInputStream_1_0.java:750)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:669)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_abstract_interface(CDRInputStream_1_0.java:890)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_abstract_interface(CDRInputStream_1_0.java:884)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.iiop.CDRInputStream.read_abstract_interface(CDRInputStream.java:307)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.se.internal.io.IIOPInputStream.readObjectDelegate(IIOPInputStream.java:228)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.se.internal.io.IIOPInputStream.readObjectOverride(IIOPInputStream.java:381)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:318)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.enterprise.iiop.IIOPHandleDelegate.getStub(IIOPHandleDelegate.java:58)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.enterprise.iiop.IIOPHandleDelegate.readEJBObject(IIOPHandleDelegate.java:38)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.ejb.portable.HandleImpl.readObject(HandleImpl.java:91)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.se.internal.io.IIOPInputStream.readObject(Native Method)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.se.internal.io.IIOPInputStream.invokeObjectReader(IIOPInputStream.java:1298)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.se.internal.io.IIOPInputStream.inputObject(IIOPInputStream.java:908)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.se.internal.io.IIOPInputStream.simpleReadObject(IIOPInputStream.java:261)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.se.internal.io.ValueHandlerImpl.readValueInternal(ValueHandlerImpl.java:247)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.se.internal.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:209)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_value(CDRInputStream_1_0.java:981)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.iiop.CDRInputStream.read_value(CDRInputStream.java:287)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.copyObject(Util.java:598)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at javax.rmi.CORBA.Util.copyObject(Util.java:314)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.telstra.nodeman.ejb._NodeMaint_Stub.getHandle(Unknown Source)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.telstra.nodeman.arch.NMAViewBeanProxy.checkBeans(NMAViewBeanProxy.java:631)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.telstra.nodeman.view.html.NMAStandardButton.handleRequest(NMAStandardButton.java:143)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.telstra.nodeman.arch.NMAViewBeanBase.handleRequest(NMAViewBeanBase.java:1573)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:824)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:637)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:595)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:772)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:446)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:324)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.telstra.nodeman.view.ViewServlet.doPost(ViewServlet.java:243)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at java.security.AccessController.doPrivileged(Native Method)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:158)
[10/Aug/2004:08:04:57] WARNING (17227): CORE3283: stderr:      at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)
The above error caused the server to use all available memory and required a reboot to proceed.
Subsequent testing against the Sun Appliucation Server 7 on Windows 2000 dev environment using the Sun Studio IDE for debugging and trace statements inserted in the code indicate that the Application Server is removing the Stateful Session Beans when they time out without an ejbPassivate event and without serializing the beans to the data-store. cache-idle-timeout-in-seconds set to 180 and removal-timeout-in-seconds set to 1800.
The server.log indicates that the beans are timing out:
[19/Aug/2004:18:15:10] WARNING ( 1664): [NRU-com.telstra.nodeman.ejb.AddressMaintBean]: IdleBeanCleanerTask finished after removing 2 idle beans
Trace statements inserted in ejbPassivate do not appear in the log.
It is my understanding that the above timeout should have caused an ejbPasssivate and serialization of the beans.
The beans have been validated using Sun Java Studio Enterprise 6 with 'EJB validate'.
My reading of the problem is that the beans are not being serialized and the error occurs when the application attempts to reference (getHandle) the bean after timeout.
Any suggestions would be appreciated.

Thanks Thorick.
I am using NRU caching. WL 7.0 SP2.
I have not defined idle-timeout-seconds in my weblogic-ejb-jar.xml. As I understand
the default value for this is 600secs. So the ejbs should be removed after this
time. Below is the
weblogic-ejb-jar.xml that I am using.
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>

<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>Cart</ejb-name>
<stateful-session-descriptor>
<stateful-session-clustering>
<home-is-clusterable>true</home-is-clusterable>
<replication-type>InMemory</replication-type>
</stateful-session-clustering>
</stateful-session-descriptor>
<transaction-descriptor>
     <trans-timeout-seconds>
          60
     </trans-timeout-seconds>
</transaction-descriptor>
<jndi-name>CartHome</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
"thorick" <[email protected]> wrote:
>
The idle-timeout-seconds property controls the timeout/removal behavior.
which stateful session cache type are you using ? LRUCache or NRUCache

Stateful session bean deploying

Hello,
          I try to deploy stateful SessionBean with WL 6.0.
          Content of my 'weblogic-ejb-jar.xml' file is:
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0
          EJB//EN' 'http://www.bea.com/servers/wls60/ejb20/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>HashtableSessionBean</ejb-name>
          <stateful-session-descriptor>
          <stateful-session-clustering>
          <home-is-clusterable>true</home-is-clusterable>
          <replication-type>InMemory</replication-type>
          </stateful-session-clustering>
          </stateful-session-descriptor>
          <jndi-name>HashtableSessionBean</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          But I still recive error like bellow:
          ####<2001-03-28 18:15:15 GMT+02:00> <Error> <J2EE> <clikra003> <myserver>
          <Application Manager Thread> <> <> <160002> <Error deploying EJB Component :
          HashtableSessionBean>
          weblogic.ejb20.EJBDeploymentException: Exception in EJB Deployment; nested
          exception is:
          javax.naming.NamingException [Root exception is java.rmi.MarshalException:
          failed to marshal public abstract void
          weblogic.jndi.internal.NamingNode.rebind(java.lang.String,java.lang.Object,j
          ava.util.Hashtable) throws
          javax.naming.NamingException,java.rmi.RemoteException; nested exception is:
           java.rmi.server.ExportException: Failed to invoke contructor for
          RuntimeDescriptor: class weblogic.rmi.internal.BasicRuntimeDescriptor;
          nested exception is:
           java.lang.reflect.InvocationTargetException]
          javax.naming.NamingException. Root exception is java.rmi.MarshalException:
          failed to marshal public abstract void
          weblogic.jndi.internal.NamingNode.rebind(java.lang.String,java.lang.Object,j
          ava.util.Hashtable) throws
          javax.naming.NamingException,java.rmi.RemoteException; nested exception is:
          java.rmi.server.ExportException: Failed to invoke contructor for
          RuntimeDescriptor: class weblogic.rmi.internal.BasicRuntimeDescriptor;
          nested exception is:
          java.lang.reflect.InvocationTargetException
          java.rmi.server.ExportException: Failed to invoke contructor for
          RuntimeDescriptor: class weblogic.rmi.internal.BasicRuntimeDescriptor;
          nested exception is:
          java.lang.reflect.InvocationTargetException
          java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError:
          weblogic/common/managedobject/JavaRemoteManageable
          at java.lang.ClassLoader.defineClass0(Native Method)
          at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
          at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
          at
          weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLo
          ader.java:304)
          at
          weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.
          java:155)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
          at weblogic.rmi.utils.Utilities.classForName(Utilities.java:209)
          at weblogic.rmi.internal.BasicDescriptor.<init>(BasicDescriptor.java:88)
          at weblogic.rmi.internal.BasicDescriptor.<init>(BasicDescriptor.java:141)
          at
          weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.j
          ava:59)
          at java.lang.reflect.Constructor.newInstance(Native Method)
          at
          weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManager.java:
          81)
          at
          weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java
          :39)
          at
          weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java
          :30)
          at
          weblogic.rmi.internal.OIDManager.getRequestDispatcher(OIDManager.java:279)
          at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:268)
          at weblogic.rmi.internal.OIDManager.replaceObject(OIDManager.java:96)
          at
          weblogic.common.internal.WLObjectOutputStreamBase2.replaceObject(WLObjectOut
          putStreamBase2.java:47)
          at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:323)
          at
          weblogic.rmi.internal.CBVOutputStream.writeObjectInternal(CBVOutputStream.ja
          va:220)
          at
          weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:213)
          at
          weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:190)
          at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:19)
          at
          weblogic.rmi.internal.BasicRemoteRef.marshalArgs(BasicRemoteRef.java:121)
          at
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :246)
          at
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :225)
          at
          weblogic.jndi.internal.ServerNamingNode_WLStub.rebind(ServerNamingNode_WLStu
          b.java:502)
          at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:123)
          at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:117)
          at
          weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
          Impl.java:483)
          at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1105)
          at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:908)
          at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          at weblogic.j2ee.Application.addComponent(Application.java:126)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          arget.java:283)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          arget.java:109)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:562)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
          48)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:285)
          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(Confi
          gurationMBeanImpl.java:409)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:287)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at
          weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
          .java:866)
          at
          weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
          .java:853)
          at
          weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:838)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:566)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
          48)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:285)
          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:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy8.addTarget(Unknown Source)
          at
          weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationM
          anager.java:486)
          at
          weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
          ionManager.java:557)
          at
          weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
          ionManager.java:504)
          at
          weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
          .java:428)
          at
          weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
          .java:380)
          at
          weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManag
          er.java:152)
          at
          weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(A
          pplicationManager.java:643)
          ####<2001-03-28 18:15:15 GMT+02:00> <Error> <J2EE> <clikra003> <myserver>
          <Application Manager Thread> <> <> <160001> <Error deploying application
          HashtableSessionBean: Could not deploy: 'HashtableSessionBean.jar'
          Possible reasons include:
          1. The bean or an interface class has been modified but
          the deployment descriptor has not been updated
          2. The database mappings in the deployment descriptor do not
          match the database definition
          3. The jar file is not a valid jar file
          4. The jar file does not contain a valid bean>
          Robert


Hello,
          <stateful-session-clustering>
          <replication-type>InMemory</replication-type>
          </stateful-session-clustering>
          Statement above belongs to 'weblogic-ejb-jar.xml' and it is right in my
          opinion.
          I have another one statement describing SessionBean which deploy it as
          stateful bean (it is 'ejb-jar.xml' file):
          <?xml version="1.0"?>
          <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
          JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
          <ejb-jar>
          <enterprise-beans>
          <session>
          <ejb-name>HashtableSessionBean</ejb-name>
          <home>com.usermgmt.sessionbeans.hashtable.HashtableSessionHome</home>
          <remote>com.usermgmt.sessionbeans.hashtable.HashtableSession</remote>
          <ejb-class>com.usermgmt.sessionbeans.hashtable.HashtableSessionBean</ejb-cla
          ss>
          <session-type>Stateful</session-type>
          <transaction-type>Container</transaction-type>
          </session>
          </enterprise-beans>
          <assembly-descriptor></assembly-descriptor>
          </ejb-jar>
          I think that everything should go right, but SessionBean is not replicated.
          Where is the problem?
          Robert
          Uzytkownik "Prasad Peddada" <[email protected]> napisal w wiadomosci
          news:[email protected]...
          > Its not stateful session descriptor from your xml file instead it is
          > stateful-session-clustering according to the docs.
          >
          > -- Prasad
          >
          > ps: For ejb questions you will get better answers if you post to ejb
          newsgroup.
          >
          >
          > <stateful-session-clustering>
          >
          >
          > ...
          >
          >
          > <replication-type>InMemory</replication-type>
          >
          >
          > </stateful-session-clustering>
          >
          >
          > Robert Zaczynski wrote:
          >
          > > Thanks for help. I resolved this problem but my Stateful SessionBean
          doesn't
          > > replicate.
          > > Have I to use any special statement or settings???
          > >
          > > Robert
          > >
          > > Uzytkownik "Prasad Peddada" <[email protected]> napisal w
          wiadomosci
          > > news:[email protected]...
          > > > Did you modify the weblogic specific deployment descriptor xml file
          after
          > > > running ejbc. If so, you should run ejbc again and then jar it up
          again
          > > and
          > > > trying deploying and your problem should go away.
          > > >
          > > >
          > > > Cheers
          > > >
          > > > -- Prasad
          > > >
          > > > "Robert Zaczyñski" wrote:
          > > >
          > > > > Hello,
          > > > >
          > > > > I try to deploy stateful SessionBean with WL 6.0.
          > > > >
          > > > > Content of my 'weblogic-ejb-jar.xml' file is:
          > > > >
          > > > > <?xml version="1.0"?>
          > > > >
          > > > > <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD
          WebLogic
          > > 6.0.0
          > > > > EJB//EN'
          > > 'http://www.bea.com/servers/wls60/ejb20/dtd/weblogic-ejb-jar.dtd'>
          > > > > <weblogic-ejb-jar>
          > > > > <weblogic-enterprise-bean>
          > > > > <ejb-name>HashtableSessionBean</ejb-name>
          > > > >
          > > > > <stateful-session-descriptor>
          > > > > <stateful-session-clustering>
          > > > > <home-is-clusterable>true</home-is-clusterable>
          > > > > <replication-type>InMemory</replication-type>
          > > > > </stateful-session-clustering>
          > > > > </stateful-session-descriptor>
          > > > >
          > > > > <jndi-name>HashtableSessionBean</jndi-name>
          > > > >
          > > > > </weblogic-enterprise-bean>
          > > > > </weblogic-ejb-jar>
          > > > >
          > > > > But I still recive error like bellow:
          > > > >
          > > > > ####<2001-03-28 18:15:15 GMT+02:00> <Error> <J2EE> <clikra003>
          > > <myserver>
          > > > > <Application Manager Thread> <> <> <160002> <Error deploying EJB
          > > Component :
          > > > > HashtableSessionBean>
          > > > > weblogic.ejb20.EJBDeploymentException: Exception in EJB Deployment;
          > > nested
          > > > > exception is:
          > > > > javax.naming.NamingException [Root exception is
          > > java.rmi.MarshalException:
          > > > > failed to marshal public abstract void
          > > > >
          > >
          weblogic.jndi.internal.NamingNode.rebind(java.lang.String,java.lang.Object,j
          > > > > ava.util.Hashtable) throws
          > > > > javax.naming.NamingException,java.rmi.RemoteException; nested
          exception
          > > is:
          > > > > java.rmi.server.ExportException: Failed to invoke contructor for
          > > > > RuntimeDescriptor: class
          weblogic.rmi.internal.BasicRuntimeDescriptor;
          > > > > nested exception is:
          > > > > java.lang.reflect.InvocationTargetException]
          > > > > javax.naming.NamingException. Root exception is
          > > java.rmi.MarshalException:
          > > > > failed to marshal public abstract void
          > > > >
          > >
          weblogic.jndi.internal.NamingNode.rebind(java.lang.String,java.lang.Object,j
          > > > > ava.util.Hashtable) throws
          > > > > javax.naming.NamingException,java.rmi.RemoteException; nested
          exception
          > > is:
          > > > > java.rmi.server.ExportException: Failed to invoke contructor for
          > > > > RuntimeDescriptor: class
          weblogic.rmi.internal.BasicRuntimeDescriptor;
          > > > > nested exception is:
          > > > > java.lang.reflect.InvocationTargetException
          > > > > java.rmi.server.ExportException: Failed to invoke contructor for
          > > > > RuntimeDescriptor: class
          weblogic.rmi.internal.BasicRuntimeDescriptor;
          > > > > nested exception is:
          > > > > java.lang.reflect.InvocationTargetException
          > > > > java.lang.reflect.InvocationTargetException:
          > > java.lang.NoClassDefFoundError:
          > > > > weblogic/common/managedobject/JavaRemoteManageable
          > > > > at java.lang.ClassLoader.defineClass0(Native Method)
          > > > > at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
          > > > > at
          > > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
          > > > > at
          > > > >
          > >
          weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLo
          > > > > ader.java:304)
          > > > > at
          > > > >
          > >
          weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.
          > > > > java:155)
          > > > > at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
          > > > > at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
          > > > > at weblogic.rmi.utils.Utilities.classForName(Utilities.java:209)
          > > > > at
          > > weblogic.rmi.internal.BasicDescriptor.<init>(BasicDescriptor.java:88)
          > > > > at
          > > weblogic.rmi.internal.BasicDescriptor.<init>(BasicDescriptor.java:141)
          > > > > at
          > > > >
          > >
          weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.j
          > > > > ava:59)
          > > > > at java.lang.reflect.Constructor.newInstance(Native Method)
          > > > > at
          > > > >
          > >
          weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManager.java:
          > > > > 81)
          > > > > at
          > > > >
          > >
          weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java
          > > > > :39)
          > > > > at
          > > > >
          > >
          weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java
          > > > > :30)
          > > > > at
          > > > >
          > >
          weblogic.rmi.internal.OIDManager.getRequestDispatcher(OIDManager.java:279)
          > > > > at
          weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:268)
          > > > > at
          weblogic.rmi.internal.OIDManager.replaceObject(OIDManager.java:96)
          > > > > at
          > > > >
          > >
          weblogic.common.internal.WLObjectOutputStreamBase2.replaceObject(WLObjectOut
          > > > > putStreamBase2.java:47)
          > > > > at
          java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:323)
          > > > > at
          > > > >
          > >
          weblogic.rmi.internal.CBVOutputStream.writeObjectInternal(CBVOutputStream.ja
          > > > > va:220)
          > > > > at
          > > > >
          > >
          weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:213)
          > > > > at
          > > > >
          > >
          weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:190)
          > > > > at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:19)
          > > > > at
          > > > >
          > >
          weblogic.rmi.internal.BasicRemoteRef.marshalArgs(BasicRemoteRef.java:121)
          > > > > at
          > > > >
          > >
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          > > > > :246)
          > > > > at
          > > > >
          > >
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          > > > > :225)
          > > > > at
          > > > >
          > >
          weblogic.jndi.internal.ServerNamingNode_WLStub.rebind(ServerNamingNode_WLStu
          > > > > b.java:502)
          > > > > at
          weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:123)
          > > > > at
          weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:117)
          > > > > at
          > > > >
          > >
          weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
          > > > > Impl.java:483)
          > > > > at
          > > weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1105)
          > > > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:908)
          > > > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          > > > > at weblogic.j2ee.Application.addComponent(Application.java:126)
          > > > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
          > > > > at
          > > > >
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          > > > > arget.java:283)
          > > > > at
          > > > >
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          > > > > arget.java:109)
          > > > > at java.lang.reflect.Method.invoke(Native Method)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > > > .java:562)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
          > > > > 48)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > > > nImpl.java:285)
          > > > > 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(Confi
          > > > > gurationMBeanImpl.java:409)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > > > nImpl.java:287)
          > > > > at
          > > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          > > > > at
          > > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
          > > > > .java:866)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
          > > > > .java:853)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:838)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > > > .java:566)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
          > > > > 48)
          > > > > at
          > > > >
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > > > nImpl.java:285)
          > > > > at
          > > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          > > > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1
          > > 523)
          > > > > at
          weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          > > > > at
          weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          > > > > at $Proxy8.addTarget(Unknown Source)
          > > > > at
          > > > >
          > >
          weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationM
          > > > > anager.java:486)
          > > > > at
          > > > >
          > >
          weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
          > > > > ionManager.java:557)
          > > > > at
          > > > >
          > >
          weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
          > > > > ionManager.java:504)
          > > > > at
          > > > >
          > >
          weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
          > > > > .java:428)
          > > > > at
          > > > >
          > >
          weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
          > > > > .java:380)
          > > > > at
          > > > >
          > >
          weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManag
          > > > > er.java:152)
          > > > > at
          > > > >
          > >
          weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(A
          > > > > pplicationManager.java:643)
          > > > > ####<2001-03-28 18:15:15 GMT+02:00> <Error> <J2EE> <clikra003>
          > > <myserver>
          > > > > <Application Manager Thread> <> <> <160001> <Error deploying
          application
          > > > > HashtableSessionBean: Could not deploy: 'HashtableSessionBean.jar'
          > > > > Possible reasons include:
          > > > > 1. The bean or an interface class has been modified but
          > > > > the deployment descriptor has not been updated
          > > > > 2. The database mappings in the deployment descriptor do not
          > > > > match the database definition
          > > > > 3. The jar file is not a valid jar file
          > > > > 4. The jar file does not contain a valid bean>
          > > > >
          > > > > Robert
          > > >
          > > > --
          > > > Cheers
          > > >
          > > > - Prasad
          > > >
          > > >
          >
          > --
          > Cheers
          >
          > - Prasad
          >
          >

Stateful Session Bean accesed by two JSPs.

Hi there,
We are having quite an issue; we have an application that stores session
state in an stateful session bean. And we have noticed some parts of the
application create a situation where is possible that two frames -and so two
jsp- access the session bean at the same time. And, of course, it´s going to
be the same instance of the session bean..... what will be the behaviour in
this case?. Will the requests be serialized, an exception will be thrown or
the EJB will be destroyed?. Not very sure of what would happen. I suppose
there could be some problems with this-. I would appreciate any help.
Many thanks. Best regards.

Hrm. EJB spec is quite clear on what will happen (RemoteException thrown) if
the second client attempts to use Stateful Session bean which is already in
use (and the bean will not be destroyed - container will simply throw an
exception after failing to acquire a lock on the bean instance without waiting
(allow-concurrent-calls option in WebLogic allows client call to wait to acquire
lock - this was probably added as a convinience feature for applications which
use frames)).
So, normally your application has to ensure that no 2 clients are able to use
the same stateful session bean concurrently, or use allow-concurrent-calls option,
which will do that for you, but the application will become non portable.
Dimitri
PS: Thanks. Maine Coon cats are the best. Ours is a 22-pound giant ;-)
Pinklon Thomas <[email protected]> wrote:
Hi Dimitri,
Thnaks a lot for the help:one thing that I do not know if it´s an issue is
that calls come from different JSPs; the strategy I have seen in another Web
application servers is trying to activate the EJB in the middle of another
transaction... In this situation, the container cannot activate the EJB,
roolback the transaction and destroys the EJB.... Would Weblogic feature
avoid this?. I will investigate on my part....
Many many thnaks. Nice cats.
"Dimitri Rakitine" <[email protected]> wrote in message
news:[email protected]...
In 6.1 you can set allow-concurrent-calls to true in this situation:

Pinklon Thomas <[email protected]> wrote:
Hi there,
We are having quite an issue; we have an application that stores
session
state in an stateful session bean. And we have noticed some parts of the
application create a situation where is possible that two frames -and sotwo
jsp- access the session bean at the same time. And, of course, it´sgoing to
be the same instance of the session bean..... what will be the behaviourin
this case?. Will the requests be serialized, an exception will be thrownor
the EJB will be destroyed?. Not very sure of what would happen. Isuppose
there could be some problems with this-. I would appreciate any help.
Many thanks. Best regards.--
Dimitri

In-memory-replace for stateful session bean

When I add "<replication-type>InMemory</replication-type>" at the
          weblogic-ejb-jar.xml file,
          the client can't call this stateful session bean and happen exception.
          If I delete "<replication-type>InMemory</replication-type>" at the
          weblogic-ejb-jar.xml, the client can call this ejb.
          How does the In-memory-replac set?
          Is there any limitations about using the In-memory-replace?
          The weblogic-ejb-jar.xml and the exception are list.
          The weblogic-ejb-jar.xml:
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0
          EJB//EN' 'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>test_stateful</ejb-name>
          <stateful-session-descriptor>
          <stateful-session-clustering>
          <home-is-clusterable>True</home-is-clusterable>
          <home-load-algorithm>round-robin</home-load-algorithm>
          <home-call-router-class-name>beanRouter</home-call-router-class-name>
          <replication-type>InMemory</replication-type>
          </stateful-session-clustering>
          </stateful-session-descriptor>
          <jndi-name>test_stateful</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          The exception:
          java.rmi.RemoteException: EJB Exception: ; nested exception is:
          java.lang.ClassCastException:
          weblogic.rmi.internal.BasicRequestDispatcher
          java.lang.ClassCastException: weblogic.rmi.internal.BasicRequestDispatcher
          <<no stack trace available>>


This is a Work as designed in my opinion
with NRU ,the container work with an eager remove algorithm, this as stated need pressure at the cache to push the container to remove the beans from the cache ,hence there will no passivation unless the max-beans-in-cache is reached, hence you can try reducing the max-beans-in-cache and see how the caching behaves , if It does not help ,chnage the Algorithm of caching or open a Service Request for us , we can look at this closely
Regards
Anis

Both type and assembly name must be specified

Hi All,
I have 3rd party dll, I am adding the ref to it in my project.
I have created a wrapper class for one of the 3rd part dll class, my wrapper class is inheriting for IPofSerializer and serilizing the object.
In my pof-config.xml file I have created a new user-type for the class in the 3rd party dll.
<pof-config xmlns="http://schemas.tangosol.com/pof">
<user-type-list>

<include>assembly://Coherence/Tangosol.Config/coherence-pof-config.xml</include>

<user-type>
<type-id>1002</type-id>
<class-name>DCBOMLib.DCStockMarketClass</class-name>
</user-type>
</user-type-list>
</pof-config>
While starting the Cache i am getting the error "Both type and assembly name must be specified", where so i find the assembly info for the type DCBOMLib.DCStockMarketClass(its a 3rd party dll)
Regards,
Akhil

Hi,
Thanks for the reply, pls find some more details below:
1. Contents of pof-config.xml
<pof-config xmlns="http://schemas.tangosol.com/pof">
<user-type-list>

<include>assembly://Coherence/Tangosol.Config/coherence-pof-config.xml</include>

<user-type>
<type-id>1001</type-id>
<class-name>Examples.ContactInfo,ContactCache.Windows </class-name>
<serializer>
<class-name>Examples.ContactInfoSer, ContactCache.Windows</class-name>
</serializer>
</user-type>
<user-type>
<type-id>1002</type-id>
<class-name>DCBOMLib.DCStockMarketClass, Interop.DCBOMLib</class-name>
</user-type>
</user-type-list>
<allow-interfaces>true</allow-interfaces>
<allow-subclasses>true</allow-subclasses>
</pof-config>
If i dont specify type-id 1002 it says unknown user type DCBOMLib.DCStockMarketClass
2. Pls find the code
public class ContactInfoSer : IPofSerializer
public object Deserialize(IPofReader reader)
string Name = reader.ReadString(0);
string Street = reader.ReadString(1);
string City = reader.ReadString(2);
string State = reader.ReadString(3);
string Zip = reader.ReadString(4);
DCBOMLib.DCStockMarketClass DCSCM = (DCBOMLib.DCStockMarketClass)reader.ReadObject(5);
reader.ReadRemainder();
return new ContactInfo(Name, Street, City, State, Zip, DCSCM);
public void Serialize(IPofWriter outo, object o)
ContactInfo cinfo = (ContactInfo) o;
outo.WriteString(0, cinfo.Name);
outo.WriteString(1, cinfo.Street);
outo.WriteString(2, cinfo.City);
outo.WriteString(3, cinfo.State);
outo.WriteString(4, cinfo.Zip);
outo.WriteObject(5, cinfo.DCSCM);
outo.WriteRemainder(null);
During runtime I am getting following exception for the below code
DCBOMLib.DCStockMarketClass dc = new DCBOMLib.DCStockMarketClass();
ContactInfo contact = new ContactInfo(txtName.Text,
txtStreet.Text,
txtCity.Text,
txtState.Text,
txtZip.Text,dc);
cache.Insert("124", contact);
Exception -
{"Missing IPofSerializer configuration (Config=file://Config\\pof-config.xml, Type-Id=1002, Type-Name=DCBOMLib.DCStockMarketClass, Interop.DCBOMLib)"}
Is it required that the 3rd party dll having DCBOMLib.DCStockMarketClass should be inheriting from Serializable or Object?
Regards,
Akhil

Non critical error: MGMT_CNRT_TT.CLEAN_UP_OLD_TICKETS_RECS must be declared

Hello!
I'm upgrading from EMGC 10.2.0.1.0 to 10.2.0.3.0. When applying the patch for Linux x86, the upgrade process works fine, but some errors appears at the "alert" log.
The errors are something like "MGMT_CNRT_TT.CLEAN_UP_OLD_TICKETS_RECS must be declared". Does anybody know why this errors appear, and what does they mean?
Thanks a lot in advance form your help!!!
HeCSa.

I've got 18 jobs in dba_jobs:
SQL> select job, log_user, schema_user, broken from dba_jobs;
JOB LOG_USER SCHEMA_USER B
102 SYSMAN SYSMAN N
103 SYSMAN SYSMAN N
104 SYSMAN SYSMAN N
105 SYSMAN SYSMAN N
106 SYSMAN SYSMAN N
107 SYSMAN SYSMAN N
108 SYSMAN SYSMAN N
109 SYSMAN SYSMAN N
110 SYSMAN SYSMAN N
111 SYSMAN SYSMAN N
112 SYSMAN SYSMAN N
78 SYS SYSMAN Y
96 SYSMAN SYSMAN N
97 SYSMAN SYSMAN N
98 SYSMAN SYSMAN N
99 SYSMAN SYSMAN N
100 SYSMAN SYSMAN N
101 SYSMAN SYSMAN N
18 rows selected.
I've seen other threads mention between 16 + 20 ish.
I'll have a look at the doc you suggest.
Thanks.
Ric.

Table must be declared

Hi!
I am using Oracle Developer and in PL/SQL Editor of a push button, in When Mouse Click Event, I have a code "insert into sample_table values (scrId, scrName);" and the error tells me that the sample_table must be declared. I am already connected to a database where sample_table can be found.
Please help! I am really new at this stuff.
Thanks in Advance.

Is the user connecting to the DB the table owner? If not, the connecting user will need privileges on the table, and "qualify" the table with the owner (unless a synonym is created).
Daniel

DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE' must be declared after 11g upgrade

Hi,
I just uograded my dev database to from 10.2.0.4 to 11.1.0.7.2. During the testing phase of the upgrade, I had come up wiht scripts to execute after the upgrade to 11g so that my utl_smtp packages will run. But now, after upgrading to 11g, when I run these scripts, I get the below error -
ORA-06550: line 4, column 33:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 4, column 3:
PL/SQL: SQL Statement ignored
ORA-06550: line 6, column 4:
PLS-00201: identifier 'DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE' must be declared
During the testing phase, I installed 11g instance and created an 11g database and then imported the 10g objects into the 11g database so as to test the application. Now, I think what happened is when I upgraded my 10g database to 11g using DBUA, it did not install APEX. I ytried to configure APEX by following instructions from this site - http://www.oracle.com/technology/obe/11gr1_db/install/apexinst/apexinst.htm and this gives me error the error -
PLS-00201: identifier 'DBMS_XDB.SETHTTPPORT' must be declared
How do I install apex?Can someone please guide me this?
Thanks

Hi, Ogan, I got this resolved.
After the upgrade by using DBUA, I tried to execute scripts to configure ACLs since my database has dependent objects. That's when I got error saying that dbms_network_acl_admin was not found.
when I queried DBA_registry , it didn't list XDB as one of the components. So, I understood this didn't get installed during the upgrade with DBUA. So, I installed XDB manually by running catqm.sql. This however created a lot of invalid objetcs which wouldnt get validated after tryign to recompile them with utlrp.sql. Most of the errors were looping chain of synonyms. Finally, I de-installed it and re-installed xdb and ran utlrp.sql to validate all the invalid objects. Now, everything is fine.
I guess xdb doesn't get installed during the dbua upgrade and maybe it needs to be installed seperately. But, that's kind of confusing because xdb is supposed to be a mandatory component in 11g. Can someone please clarify this?

Error: Element type "stateful-session-descriptor" must be declared ?

Similar Messages

Maybe you are looking for