Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
The moose likes BEA/Weblogic and the fly likes Error encountered while doing Migration from WLS 8.1 to WLS 10.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Error encountered while doing Migration from WLS 8.1 to WLS 10.0" Watch "Error encountered while doing Migration from WLS 8.1 to WLS 10.0" New topic
Author

Error encountered while doing Migration from WLS 8.1 to WLS 10.0

shobit shrivastava
Greenhorn

Joined: Dec 19, 2006
Posts: 7
Hello All ,

We are trying to do a WLS migrate(8.1 to 10.0) for a java/j2ee based application. We did not face any issues while compling application code (using jdk 1.5 & weblogic.jar of WLS 10.0) but while running the ant build script , we encountered an error while executing below part



Following is the error , which we encountered



Any insight on the above scenario will be a great help.

Regards
Shobit
Ed Ward
Ranch Hand

Joined: Jan 30, 2006
Posts: 147
I suspect this is more of an Ant issue than a Weblogic one. But a guess would be that the variables are being expanded in such a way that appc is seeing more than one input file.
What is the value of ${_appc.input} when Ant gets to it?
It should be a single jar file I think.
Are ${bmwslc.param.options} and ${appc.additional.options} set with valid appc option parms?

It would be kind of a pain, but for debugging purposes try replacing (one by one) all the variables in the <arg> element with hardcoded strings and see what happens.
shobit shrivastava
Greenhorn

Joined: Dec 19, 2006
Posts: 7
Thanks Edward for your suggestion !!.

I have already followed the hard coded string approach suggested by you before posting the problem in forum but no success in nailing down the problem.

All the arguments looks correct to me while debugging . here is the summary of echo statements

${appc.additional.options} =""
${bmwslc.param.options} ="-forceGeneration"
${_appc.input}="test_ear-generic.ear"

I am dumb struck because all the parameters seems to be correct

Please suggest any other thoughts , which you have in mind .

Thanks in advance !

Regards
Shobit


Ed Ward
Ranch Hand

Joined: Jan 30, 2006
Posts: 147
Kinda of at a loss then if you're sure everything is setup right. Maybe there's a problem with the ear your passing in or with running appc via the Ant <java> task.
Have you tried running appc from the command line on this ear?
Weblogic does have an Ant appc task: <wlappc>

See.Weblogic wlappc task

Though I have never used it.

Sorry am unable to be of more assitance.
shobit shrivastava
Greenhorn

Joined: Dec 19, 2006
Posts: 7
Hello Edward !

Thank you again !

I am able to get much more about the stack trace but unable to comprehend it much . please see the stack trace below :



The other approach suggested by you i.e. using wlappc task (Weblogic specific appc task) by executing below script file


Though i was not completely successful to compile the ear file but the error popped up was different (about some missing jar) files) not the Incorrect appc command-line error .

So above analysis suffice that Ear file is correct . there could be problem with Ant . Could you please see the above stack trace of error and infer any thing ?

Any thought will be a great help

Regards
Shobit
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Error encountered while doing Migration from WLS 8.1 to WLS 10.0
 
Similar Threads
Doubt in static import
compileing with .jar file
Compiler flag
time,date+progress bar
Error encountered with weblogic.appc in weblogic 9.0