Studies --> Weblogic --> Problems

Weblogic :
weblogic server 9.2:

1). I installed the weblogic by taking the default jdk and development mode.


2). Move to configuration wizard and create a domain.
* Start server : Dir:\bea\user_projects\domains\mydomain\bin >startWebLogic.cmd
for websphere move upto ibm\websphere\appserver\bin and type startServer server1 -username system -password password. ( or u can start the service).

* Diratasource (database) should mention in Dir:\bea\user_projects\domains\mydomain\config\jdbc directory.
* Similarly in jboss it is jmetro-ds.xml in default deploy directory.
* In websphere it is Dir:\Program Files\IBM\WebSphere\AppServer\lib\ext directory.




3).Now I am going to configure the weblogic ldap.

A1) .while starting the server I got the following exception:
startWebLogic.cmd , It started fine now ,

nOW i started to configure the ldap users.




A4). [EJB:011020]The database table: AW_AVAILACT does not contain the columns: actSpeakerOrgRoleIds. Please consult your database mappings in the weblogic-cmp-rdbms.xml deployment descriptor and ensure these match your database schema.

This is due to adding new column to the above talbe. in weblogic-cmp-rdbms.xml we will map the ejb and its columns.




A5). java.lang.NoSuchMethodException: org.apache.axis.encoding.ser.ArraySerializerFactory.create(java.lang.Class, javax.xml.namespace.QName)
at java.lang.Class.getMethod(Class.java:1581)
at org.apache.axis.encoding.ser.BaseSerializerFactory.createFactory(BaseSerializerFactory.java:254)
at org.apache.axis.deployment.wsdd.WSDDService.deployTypeMapping(WSDDService.java:542)


sOL: No sol ,

A6) After this while running testcases i got java.lang.OutOfMemoryError: Java heap space


for that we set the ANT_OPTS="-Xms256m -Xmx256m" as environment variable.

SolL: set this in the command prompt where u r running ur tests.



A7). Cannot create LoginContext. java.net.MalformedURLException: port expected: t3://ldap://localhost:7001/


Actually tehy are getting the logincontext from teh util file there while getting
context they are getting ldapconfig tag. but in the ldap config tag we have somthing wrong.
So i HARD CODED THAT.

We have JNDI SERVER WITH EACH AND EVERY APPLICATION SERVER ( RMI REGISTRY SERVICE IS AN
OPEN SOURCE) USIG THIS WE ARE GETTING THE OBJECTS.







Other problems:
---------------

1). User login module error, i.e if we use realm name to sync users. it will move to

login-config(jboss) file and check the login module corresponding to that perticular realm

For we application realm is metioned in web.xml and jboss.xml files i think.