Same container, different ear files, remote lookup failing!

I'm having severe problems with my ears! I used to have all my EJBs in one ear file and everything worked hunky dory. Now I have separated out various components into their own ear files as they may be deployed into a separate box and also this eases group development. My problem is that some (most) of the remote lookups don't work. I'm getting a Class cast exception when i use the narrow() method.
I have tried all the methods I can think of now and I'm getting desperate! Initially when all the beans were in the same ear file I used the coded reference for the lookup. This did not work across separate ear files so I replaces the coded reference in the lookup() method to the JNDI name. Now this works for some lookups but not others. Invariably a client application running in the container in a separate ear will work no problem. However a session bean using the same code as the client can not succeed in referencing another bean.
I'm baffled here because the lookup itself appears to succeed (if I but a garbage name in the lookup method it returns "name not found"). The error I'm getting is class cast exception! Occasionally though it does work - by that I mean it works for some inter-ear references but not others ie it's not intermittant.
Can anyone shed some light on the correct/best method to lookup a remote reference to a EJB from an EJB living in a different ear file in the same container?

Found the problem!
I was using jdk 1.3.0_02 when I should have been using
jdk 1.3.1_01
painful...

Similar Messages

Communication between processes in different ear files

I have two processes that I created in WLI 10. Each process is deployed to the same Weblogic 10 server but they are in different ear files. How can I send messages between the two WLI processes without making a web service call? Im trying to find an efficient way to communicate between the two processes. Since there is alot of overhead with web service calls I am trying to stay away from using web service calls. I would like to use a WLI control but I cant find a control that will communicate with another process outside of an ear file without using web service calls.
Any help is greatly appreciated!
Thanks -
John

There are two ways of doing it
1. Have the first WLI process put the message to the queue and have the second WLI process to start by pickin up messages from the queue
2. Generate the wsdl out of the Second Process, create a Process Control and call the second process using the Process Control.
The Choice depends on the frequency of calls and payload. If the frequency and payload is high, it is preferred to use the first approach.
Edited by: varun.iyer on Sep 3, 2009 3:44 PM

Different EAR file size for 2 exactly the same set of source codes

Hi All,
I have 2 exactly the same sets of source codes for my application that were compiled in 2 different environment (say SIT and UAT; both using the same jdk versions), is it possible that the EAR files after build will be different in size too?
Can you suggest any online reading materials that I can read regarding this?
Thank you very much
Eddie

Hi Arun,
Thanks for the answer.
I already did a comparison of the 2 application, they are exactly the same (i only copied the source including the jars from PROD to UAT). I also did a comparison between the 2 EAR files generated (exploded the EAR file and compare each of the files), they are the same. My aim actually is to compile the application in Machine1 and deploy it in Machine2, I am just puzzled why the 2 EAR files generated by the 2 machines are different in size. Does it has something to do with the compression and compiling?
Thanks,
Eddie

Same source, different jar file sizes

What could be creating this discrepancy in jar file sizes on two machines with exactly the same versions of SDK etc installed.
Machine 1 - obfuscated jar size 148Kb
Source moved to Machine 2 - obfuscated jar size 222Kb
Source moved back to Machine 1, mods made, - obfuscated jar size 143Kb
Source copied to Machine 2, NO mods, - obfuscated jar size 138Kb
I want to retire Machine 1, and in fact Machine 2 is due to be re-purposed as well when my new shiny one arrives but I am worried I won't be able to get my file sizes as small as possible or at least cram as much as possible in so I would like to know what sort of things impact the packaging process.
Thanks
Kathydb

When you sync photos with iTunes it automatically optimizes the photo size for the screen on the device it is syncing it to. Photo Stream also has some of this functionality built into it as well although a full resolution photo will be sent to iPhoto on Mac computers. Photos taken with different devices will also have different file sizes depending on how many megapixels the camera on the device has.

How to deploy ear file in OATS

hi gems..good afternoon...
I need to deploy my application's EAR file in OATS to test it.
I have installed OATS 12.0 version and also have started the demo setup i.e the medrec application from the documentation.
Now, how can I setup my application in OATS...I have the ear file and the database credentials.
Pls guide me...thanks a lot...

gogol wrote:
Thanks a lot Jean-Baptiste for your reply..
That means cant we deploy any other ear file (other than medrec application, default application during installation) if we dont install weblogic separately from a licensed version??Exactly.
>
actually the confusions i faced are:
after installation of OATS, when i hit the url "http://localhost:7011/console" and gave the credentials "weblogic/welcome1", then it shows the medrec.ear, physician.ear etc are deployed.
Those are demo samples provided with ATS
Again when i hit the url "http://localhost:8088/console" and gave the credentials "oats/<password>", then it shows the oats_ee.ear is deployed.
Thats why I am confused, how the ear has been deployed....there are two locations available with different credentials.2 different locations because 2 different applications not running in the same container (different port, different url)
>
I am followng the Getting Started documentation, but i couldnot clear the concept.Best is to use your own licensed weblogic installation. Of course, technically speaking, you can do it, but be careful not to be out of compliant.
Cheers
JB

Refering to JNDI name in other EAR file

Hi, there:
Our team is trying to write a session bean as a factory to serve
other beans. Even the JSP (or other clients) can find the correct
session bean residing on different ear file, the factory can't return
properly when the returning parameter is a java object (it works fine
if we only return int/string/etc). Is there a work-around to make
these work?
Thanks,
-Daniel

Hi Ravi,
Can you please post the error message and stack trace? Also what version of WLS are you
using? The more relevant information you can give me, the more likely I'll be able to
help you.
- Matt
ravichandran wrote:
Hi Matthew,
Thank u for very quick response, the error is class cast exception and these objects
are serialized and kept in ear. ur solution will be highly appreciated.
regards
ravi
Matthew Shinn <[email protected]> wrote:
Hi,
What error are you getting (please include full error message & stack trace)?
Also,
is the object you are returning Serializable?
- Matt
ravi wrote:
Hello Daniel
I also have the same problem, do u have any solutions, please let me know,I was
struggling for more than ten days.
regards
ravi
[email protected] (Daniel) wrote:
Hi, there:
Our team is trying to write a session bean as a factory to serve
other beans. Even the JSP (or other clients) can find the correct
session bean residing on different ear file, the factory can't return
properly when the returning parameter is a java object (it works fine
if we only return int/string/etc). Is there a work-around to make
these work?
Thanks,
-Daniel

How to Persis session between two ear files

Can anybody tell me how to persists session between two ear files?
Please Help its urgent!!
Rahul

Rahul -- there's nothing as a J2EE spec requirement or even a proprietary feature of OC4J/OracleAS which will enable this.
If you have two different EAR files, then they are two different applications, and each will have their own session which can't be shared amongst each other.
If you have data which needs to be shared across different applications then you could either put it on a shared file system or write it to a database which you can then read from in the other application.
One way to do this is to implement the HttpSessionAttributeListener interface which will be called when object are added/removed/updated from a session, and then make a determination on whether the new object needs to be stored in a common place to facilitate sharing between applications.
This is more likely to be a hackaround and ideally you'd examine why you want to share session state across applications and rearchitect so you don't need to do it -- but if you want to try a solution without a major revisiting of the whole application, then perhaps it's an option.
cheers
-steve-
cheers
-steve-

Error while using LiveCycle java APIs with Http servlets:"Remote EJBObject lookup failed for ejb/Inv

Hi all,
When i try to run more than one servelt of the Quick Start samples that using Livecycle Java APIs and i get an error of "Remote EJBObject lookup failed for ejb/Invocation provider" from any servelt i run.
I try some Quick samples which is not servelts (java class) and it works fine, which makes me sure that my connection properties is true.
Environment:
The LiveCycle is based on "Websphere v6.1", and i use "Eclipse Platform
Version: 3.4.1".
i install "tomcat 5.5.17" to test the servelts in developing time through Eclipse.(only for test in developing time not for deploy on )
The Jars i added in the classpath:
adobe-forms-client.jar
adobe-livecycle-client.jar
adobe-usermanager-client.jar
adobe-utilities.jar
ejb.jar
j2ee.jar
ecutlis.jar
com.ibm.ws.admin.client_6.1.0.jar
com.ibm.ws.webservices.thinclient_6.1.0.jar
server.jar
utlis.jar
wsexception.jar
My code is :
Properties ConnectionProps = new Properties();
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_EJB_ENDPOINT, "iiop://localhost:2809");
ConnectionProps.setProperty ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,ServiceClientFactoryProperties.DSC_ EJB_PROTOCOL);
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE,ServiceClientFa ctoryProperties.DSC_WEBSPHERE_SERVER_TYPE);
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, "Administrator");
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, "password");
ConnectionProps.setProperty("java.naming.factory.initial", "com.ibm.ws.naming.util.WsnInitCtxFactory");
//Create a ServiceClientFactory object
ServiceClientFactory myFactory = ServiceClientFactory.createInstance(ConnectionProps);
//Create a FormsServiceClient object
FormsServiceClient formsClient = new FormsServiceClient(myFactory);
//Get Form data to pass to the processFormSubmission method
Document formData = new Document(req.getInputStream());
//Set run-time options
RenderOptionsSpec processSpec = new RenderOptionsSpec();
processSpec.setLocale("en_US");
//Invoke the processFormSubmission method
FormsResult formOut = formsClient.processFormSubmission(formData,"CONTENT_TYPE=application/pdf&CONTENT_TYPE=app lication/vnd.adobe.xdp+xml&CONTENT_TYPE=text/xml", "",processSpec);
List fileAttachments = formOut.getAttachments();
Iterator iter = fileAttachments.iterator();
int i = 0 ;
while (iter.hasNext()) {
Document file = (Document)iter.next();
file.copyToFile(new File("C:\\Adobe\\tempFile"+i+".jp i++;
short processState = formOut.getAction();
...... (To the end of the sample)
My Error was:
com.adobe.livecycle.formsservice.exception.ProcessFormSubmissionException: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider
at com.adobe.livecycle.formsservice.client.FormsServiceClient.processFormSubmission(FormsSer viceClient.java:416)
at HandleData.doPost(HandleData.java:62)
at HandleData.doGet(HandleData.java:31)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
a

I assume here that your application is deployed on a different physical machine of where LCES is deployed and running.
Do the following test:
- Say that LCES is deployed on machine1 and your application is deployed on machine2. Ping machine1 from machine2 and note the ip address.
- Ping machine1 from machine1 and note the ip address.
The two pings should match.
- Ping machine2 from machine1 and note the ip address.
- Ping machine2 from machine2 and note the ip address.
The two pings should match.
Usually this kind of error would happen if your servers have internal and external ip addresses.

How to deploy ear file with jar file and war file with different names

Hi,
As part of weblogic migration from WL 6.1 sp3 to WL 10, Iam facing some problem.
Problem:
I have one ear file(abc.ear) to deploy which contains one jar file(xyz.jar) and one war file(pqr.war).
In config.xml file of WL 6.1, it was mentioned as :
<Application Deployed="true" Name="abc" Path="./config/mydomain/applications/abc.ear">
<EJBComponent Name="xyz" Targets="myserver" URI="xyz.jar"/>
<WebAppComponent Name="pqr" Targets="myserver" URI="pqr.war"/>
</Application>.
The above is working fine.
But in config.xml file WL10,I cannot mention the same.
I need to have different application anmes for ear,jar and war.If I deploy as a ear file,the jar and war files are deployed with the same ear file name.
I tried the following options:
1) Deploying as a ear file by adding <sub-deployments>
2) Deploying both war and jar seperately which is not recommended in my application.
Please provide the content I should place in the config.xml so that everything works fine correctly.
Any help is appreciated.

Hi,
As part of weblogic migration from WL 6.1 sp3 to WL 10, Iam facing some problem.
Problem:
I have one ear file(abc.ear) to deploy which contains one jar file(xyz.jar) and one war file(pqr.war).
In config.xml file of WL 6.1, it was mentioned as :
<Application Deployed="true" Name="abc" Path="./config/mydomain/applications/abc.ear">
<EJBComponent Name="xyz" Targets="myserver" URI="xyz.jar"/>
<WebAppComponent Name="pqr" Targets="myserver" URI="pqr.war"/>
</Application>.
The above is working fine.
But in config.xml file WL10,I cannot mention the same.
I need to have different application anmes for ear,jar and war.If I deploy as a ear file,the jar and war files are deployed with the same ear file name.
I tried the following options:
1) Deploying as a ear file by adding <sub-deployments>
2) Deploying both war and jar seperately which is not recommended in my application.
Please provide the content I should place in the config.xml so that everything works fine correctly.
Any help is appreciated.

Lookup ejb in another application in same container

Hi,
The 1012 ejb faq http://www.oracle.com/technology/tech/java/oc4j/1012/collateral/OC4J-EJB-FAQ-101202.pdf states:
"If you want to access an EJB in another application in the same OC4J container you do not have to use RMIInitialContextFactory and you can make the application that contains your application as the parent of your application from your you are trying to access EJBs from e.g. ..."
Question: The FAQ implies that the "parent" attribute is NOT necessary to facilitate this situation and RMIInitialContextFactory may be used - is this correct? I have not found any examples that demonstrate how to do this as elsewhere in the Oracle doco they seem to imply that "parent" must be used (but not in 10.1.3). Can anyone please clarify this and/or what works and what doesn't?
Note: The lookup of remote ejb from another application in same container does work without the parent attribute, its just subsequent calls from a 3rd application or redeploy breaks.
My problem: I get a ClassCastException when :
a) lookup remote EJB (in application A) following redeploy of application B
b) the next invocation of the application A method from client application C
Thanks for any advice,
Paul

Your understanding is correct.
If you make application a to be the parent application of app b; then app b could access app a without using RMIInitialContext.
Also you could use RMIInitialContext to obtain the object without using "parent application" approach, example:
Hashtable env = new Hashtable();
env.put("java.naming.factory.initial",
"com.evermind.server.rmi.RMIInitialContextFactory");
env.put("java.naming.provider.url","ormi://remotehost/bmpapp");
env.put("java.naming.security.principal","SCOTT");
env.put("java.naming.security.credentials","TIGER");
Context context = new InitialContext(env);
Object homeObject =
context.lookup("java:comp/env/EmployeeBean");
For this servlet example, you also need to declare <ejb-ref> elements in the web.xml file:
<ejb-ref>
<ejb-ref-name>EmployeeBean</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>bmpapp.EmployeeHome</home>
<remote>bmpapp.Employee</remote>
</ejb-ref>
In addition, orion-web.xml, must include a mapping from the logical name EmployeeBean to the actual JNDI name where the EJB is bound, as shown in the following example:
<ejb-ref-mapping name="EmployeeBean" location="bmpapp/EmployeeBean" />
Hope this helps,
-Frances

EJB(EAR file) lookup from separate WAR file

Hi
I have 2 applications (EAR and WAR) deployed in an OC4J instance using Oracle 10g. All my EJB components are in my EAR file and all my front-end/servlet component are in the WAR file. My lookup in the servlet fails, like:
05/01/21 13:47:05 javax.naming.NameNotFoundException: SessionEJB not found
05/01/21 13:47:05 at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:149)
05/01/21 13:47:05 at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:248)
05/01/21 13:47:05 at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:119)
05/01/21 13:47:05 at javax.naming.InitialContext.lookup(InitialContext.java:347)
05/01/21 13:47:05 at efdw.eap.servlet.SessionEJBAction.execute(SessionEJBAction.java:48)
05/01/21 13:47:05 at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
05/01/21 13:47:05 at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
05/01/21 13:47:05 at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
05/01/21 13:47:05 at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
05/01/21 13:47:05 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
05/01/21 13:47:05 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
05/01/21 13:47:05 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)
05/01/21 13:47:05 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
05/01/21 13:47:05 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
05/01/21 13:47:05 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:208)
05/01/21 13:47:05 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:125)
05/01/21 13:47:05 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
05/01/21 13:47:05 at java.lang.Thread.run(Thread.java:534)
EJB reference in web.xml looks like:
<ejb-ref>
<ejb-ref-name>SessionEJB</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.app.bean.SessionEJBHome</home>
<remote>com.app.bean.SessionEJB</remote>
</ejb-ref>
I've added the "parent" attribute in server.xml, something like:
<application name="myapp" path="../applications/myapp.ear" auto-start="true" />
<application name="myweb" path="../applications/myweb.ear" auto-start="true" parent="myapp" />
but the sever.xml file gets reset and there is no parent attribute in the file
lookup in my servlet:
Context ctx = new InitialContext();
Object objref = ctx.lookup("SessionEJB");
sessionEJBHome = (SessionEJBHome)PortableRemoteObject.narrow(objref, SessionEJBHome.class);
beanRemote = sessionEJBHome.create();
I also tried using the jndi.properties file and by specifying context attributes (PROVIDER_URL,INITIAL_CONTEXT_FACTORY,..) nothing worked.
Is there a way I can configure the jndi tree like in weblogic? How do I need to configure the lookup?

Hi Naga,
You have to lookup the ejb as follows:
Object objref = ctx.lookup("java:comp/env/ejb/SessionEJB");
location tag in orion-ejb-jar.xml for the EJB determines where the JNDI-name to which this bean will be bound documented in EJB Guide at http://download-west.oracle.com/docs/cd/B14099_01/web.1012/b15505/dtdxml001.htm#sthref1130
<ejb-ref-mapping ... > in orion-web.xml :
This element creates a mapping between an EJB reference, defined in an <ejb-ref> element, and a JNDI location when deploying.
The <ejb-ref> element can appear within the <web-app> element of orion-web.xml or web.xml and is used to declare a reference to an EJB.
-Debu

Can not lookup EJB from another EAR file, the ClassCastException returned

Hi,
     I try to call EJB module in A.ear from Servlet in another EAR file(B.ear) the ClassCastException returned on the context.lookup() code . So when i create a Dynamic Web Project(With the same code as Servlet in B.ear) and pack it in A.ear(The same EAR file with EJB module), it work fine. I have no idea. Could you please suggest me.
The ClassCastException : incompatible with interface ..... return on
HelloManBeanLocalHome home=(HelloManBeanLocalHome) ctx.lookup("localejbs/sap.com/HelloMan_EAR/HelloManBean");
The entire code is below :
          try {
               InitialContext ctx=new InitialContext();
               HelloManBeanLocalHome home=(HelloManBeanLocalHome) ctx.lookup("localejbs/sap.com/HelloMan_EAR/HelloManBean");
               HelloManBeanLocal remote=home.create();
               lookupText=remote.helloMan("Test");
          } catch (Exception e) {
               // TODO: handle exception
               e.printStackTrace(out);
Many Thanks

Hi Saleem Mohammad.
           Thank a lot for your post. I got this idea from your link. The below code work fine.
          try {
               InitialContext ctx=new InitialContext();
               Object obj= ctx.lookup("localejbs/sap.com/HelloMan_EAR/HelloManBean");
                ClassLoader homeCl = obj.getClass().getClassLoader();
                Class<?> localHome = homeCl.loadClass(HelloManBeanLocalHome.class.getCanonicalName());
                java.lang.reflect.Method method = localHome.getMethod("create");
                Object homeObj = (Object)method.invoke(obj);
                ClassLoader localCl=homeObj.getClass().getClassLoader();
                Class<?> local = localCl.loadClass(HelloManBeanLocal.class.getCanonicalName());
                Class args[] = {String.class};
                java.lang.reflect.Method localMethod=local.getMethod("helloMan",args);
                Object params[]={"Thongie"};
                Object localObj = (Object)localMethod.invoke(homeObj,params);
                lookupText=(String)localObj;
          } catch (Exception e) {
               // TODO: handle exception
               e.printStackTrace(out);

Deployment of same EAR files to two separate clustered domains

I am currently running all my portal applications and business objects from within one 8.1 clustered environment.
However I would like to move to an architecture where we use two 8.1 clustered server domains.
Where:
Clustered domain 1 is used to service requests from back office applications from within the enterprise and
Clustered domain 2 used to service requests for external facing applications from the portal jpf's.
The deployment issue which concerns me is that each cluster will require an identical deployment of the same ear files.
The datasources for each of the ear's will point to a common database.
This solution is prefered over that of deploying the ear files to just one clustered domain and calling the application from the other clustered domain
via the remote interface, as this would incure code changes and all the associated testing etc.
I'd like to find out if there are any issues on of concurrency with this deployment model ?
The business objects in the ears are comprised of mainly CMP EJB's and statless session beans.
How will the container of each cluster manage the DB concurrency of the CMP EJB's when the datasource's of the ear files in each clustered domain
point to the same DB ? Will this cause any concurrency conflicts?

Sounds like you have some code that is not threadsafe. Instances are interacting, probably because you are using static data that is being shared between running instances in the same jvm. If so, convert to instance data if your code is the cause.
Check this line of code, it may be the cause:
at jep.MySimpleEventQueue.dispatchEvent(MySimpleEventQueue.java:59)

8.1.5 - EAR file fails to Deploy - start() failed

Hello,
I am currently trying to deploy an EAR file I created in Weblogic Workshop on a running 8.1.5 Solaris 8 server that has a set of applications and services deployed on it already.
The domain was not initially created with workshop applications enabled, however I did extend the domain after a few class not found errors seem to indicate that was what I should do.
I have created an EAR and a WAR file containing the same code and deployed each of them successfully on a standalone Solaris 8 machine, on domains either created for workshop or extended for it.
This is the error I am seeing in the console, when I try to deploy on our current set up:
weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: start() failed.
Module: NGA_AOI Error: java.lang.ExceptionInInitializerError
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2440)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2155)
at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2254)
at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2149)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2401)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
No Exception Messages
Any ideas would be appreciated, I have no idea what this is trying to tell me.
Thanks,
Cash

Here is everything I get from stdout/stderr:
Note: The first exception is not related to deployment, but must be something with our currently deployed apps.
<Nov 17, 2006 1:55:11 PM GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_08-b03 from Sun Microsystems Inc.>
<Nov 17, 2006 1:55:12 PM GMT> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<Nov 17, 2006 1:55:12 PM GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic Integration 8.1 SP5 Wed Sep 21 21:56:54 PDT 2005 643163>
<Nov 17, 2006 1:55:12 PM GMT> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at /h/data/local/I3CMT/data/I3/./config.xml.>
<Nov 17, 2006 1:55:17 PM GMT> <Info> <Management> <BEA-141087> <Property: jspc.skipVersionCheck is not a recognized MBean attribute or special property used for Management. It is probably being used by subsystems and will continue to work as expected if it is a supported option.>
====== InitializeServlet: entering init
==== datadir is /h/data/local/ITSMT/data/
*=*=* Driver name is com.sybase.jdbc2.jdbc.SybDriver
*=*=* Conn URL is jdbc:sybase:Tds:SDS:3000/IMDB?ServiceName=IMDB&BE_AS_JDBC_COMPLIANT_AS_POSSIBLE=true&SELECT_OPENS_CURSOR=true
*** Unable to properly initialize ItsInfo
=== exception is access denied (java.util.PropertyPermission kodo.properties read)
java.security.AccessControlException: access denied (java.util.PropertyPermission kodo.properties read)
     at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
     at java.security.AccessController.checkPermission(AccessController.java:401)
     at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
     at java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1276)
     at java.lang.System.getProperty(System.java:612)
     at com.solarmetric.conf.ConfigurationImpl.loadDefaults(ConfigurationImpl.java:345)
     at kodo.jdbc.conf.JDBCConfigurationImpl.<init>(JDBCConfigurationImpl.java:301)
     at kodo.jdbc.conf.JDBCConfigurationImpl.<init>(JDBCConfigurationImpl.java:81)
     at kodo.jdbc.runtime.JDBCPersistenceManagerFactory.getPersistenceManagerFactory(JDBCPersistenceManagerFactory.java:43)
     at gccs.i3.imagery.itsmt.beans.ItsInfo.setPersistenceManager(ItsInfo.java:230)
     at gccs.i3.imagery.itsmt.beans.ItsInfo.initializeServers(ItsInfo.java:179)
     at gccs.i3.imagery.itsmt.beans.ItsInfo.init(ItsInfo.java:88)
     at gccs.i3.imagery.itsmt.beans.ItsInfo.<init>(ItsInfo.java:54)
     at gccs.i3.imagery.itsmt.beans.ItsInfo.getInstance(ItsInfo.java:71)
     at gccs.i3.imagery.itsmt.servlets.InitializeServlet.init(InitializeServlet.java:108)
     at javax.servlet.GenericServlet.init(GenericServlet.java:258)
     at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1094)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:970)
     at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:949)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:888)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3430)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3375)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3356)
     at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:6208)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:864)
     at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2134)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2175)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2122)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3099)
     at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1768)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:351)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
     at weblogic.Server.main(Server.java:32)
log4j:WARN No appenders could be found for logger (org.apache.struts.util.PropertyMessageResources).
log4j:WARN Please initialize the log4j system properly.
weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: start() failed.
     Module: AOI     Error: java.lang.ExceptionInInitializerError
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2440)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2155)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2254)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2149)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2401)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: start() failed.
     Module: AOI     Error: java.lang.ExceptionInInitializerError
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2413)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: start() failed.
     Module: AOI     Error: java.lang.ExceptionInInitializerError
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2440)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2155)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2254)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2149)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2401)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: start() failed.
     Module: AOI     Error: java.lang.ExceptionInInitializerError
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2413)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Thanks in advance,
Cash

Remote creation of MBean deployed in EAR file : loader's ObjectName ??

I am trying to implement a client which connects to the MBean server
running in weblogic and then creates an instance of an MBean deployed
inside an ear file. However, since the class files of the MBean are
inside the ear file (and NOT in the "serverclasses" directory), it
looks as if I needed to specify a non-default classloader when calling
RemoteMBeanServer.createMBean(...).
--> How can I determine the ObjectName of the correct loader (on
runtime) ?
(I am running weblogic 6.1 SP2 on Win2K)
import javax.naming.Context;
import javax.management.*;
import weblogic.jndi.*;
import weblogic.management.*;
public class TestClient {
public static void main(String[] args) {
String host = "localhost";
int port = 7001;
String username = "system";
String password = "password";
String serverName = "examplesServer";
try {
// get the remote MBean server
Environment env = new Environment();
env.setProviderUrl("t3://" + host + ":" + port);
env.setSecurityPrincipal(username);
env.setSecurityCredentials(password);
Context ctx = env.getInitialContext();
MBeanHome home = (MBeanHome)ctx.lookup(MBeanHome.JNDI_NAME
+ "." + serverName);
ctx.close();
RemoteMBeanServer remoteServer =
(RemoteMBeanServer)home.getMBeanServer();
// remotely create a new instance of our MBean, deployed
in an ear file (NOT the "serverclasses" directory !!)
String domain = "examples";
String mBeanClassName = "basic.SimpleStandard";
String mBeanName = mBeanClassName + "_" +
System.currentTimeMillis();
ObjectName mBeanObjectName = new ObjectName(domain +
":Name=" + mBeanName + ",Type=" + mBeanClassName);
//ObjectName loaderObjectName = ?? that's my question ??;
//ObjectInstance mBeanInstance =
remoteServer.createMBean(mBeanClassName, mBeanObjectName,
loaderObjectName);
ObjectInstance mBeanInstance =
remoteServer.createMBean(mBeanClassName, mBeanObjectName); // this
throws "javax.management.ReflectionException: The MBean class could
not be loaded by the default loader repository"
} catch (Exception e) {
e.printStackTrace();

Atlast it worked. The problem was that in my ejb-jar.xml I was referring to 2_0.dtd. I have changed that to 2.1 and it worked.
Older ejb-jar.xml had:
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "C:/jboss-4.0.1sp1/docs/dtd/ejb-jar_2_0.dtd">
I changed that to:
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
And it worked.
-Sathish

Same container, different ear files, remote lookup failing!

Similar Messages

Maybe you are looking for