Problem during deploying

Error in compiling Flex application: Error: A function in the code exceeds the 64K byte limit (actual size = '72792'). Since the problem occurs in the compiler-generated deferred instantiation code, please refactor/componentize portions of this document.
(/usr/sap/APD/JC00/j2ee/cluster/server0/GUIMachine_Business_Packages/MPSEZ_PMS_23879/FLEX_COMPILATION_FOLDER/AADTEH.mxml:19)
Failed to compile AADTEH.mxml
Kindly help
Thanks
Nivedita

Hi,
This is well know problem and it will be solved with Flex2 Compiler.
see the below wiki
[https://www.sdn.sap.com/irj/sdn/wiki?path=/display/vc/64kbytelimit]
Regards,
Govindu

Similar Messages

Problem during deployment of axis (stock) examples

Hi all
I am getting problem during the deployment of stock example given in the apache site.
Even i am not getting the right response from the URL
http://localhost:8080/axis/services/Version?method=getVersion
and
http://localhost:8080/axis/EchoHeaders.jws?method=list.
I am using tomcat 4.1 and JDK1.4.
I have set all the jar files in the axisclasspath.
At the deployment i am using the commond
C:\tomcat4\webapps\axis\WEB-INF\classes>java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -lhttp://localhost:8080/axis/services/AdminService samples\stock\deploy.wsdd
and getting fault as
Processing file samples\stock\deploy.wsdd
Exception: AxisFault
faultCode: {http://xml.apache.org/axis/}Server.NoService
faultSubcode:
faultString: The AXIS engine could not find a target service to invoke! targetService is null
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:Divyakant-verma
If anybody has solution please let me know
Thanks in advance
Divyakant Verma

I too am having the same issue and I am using the Java2WSDL and the WSDL2Java to create both the WSDL and the WSDD and I still get Server.NoService when I try to use the AdminClient to deploy the wsdd?
I have tried using both 1.2 and 1.2.1.
I am going to try to use an older verison to see if this is a bug..
If any one know the answer to this deployment problem please speak up.

Problem during deploying bw iview from visual composer module on Portal.

Hi all,
we are working on Portal 6.0 sp 11 and using VC 6.0 sp 4 for developinrg R3 and Bw iviews on Visual composer. There is no problem in deploying the r3 iviews on the portal but in case of BW (3.0 and 3.5 ) iviews while deploying it to portal gives the following
Error in executing a process for compilation, .\GUIMachine_Business_Packages\TESTRED_24360\com.autogen.guimachine_1104120045\src.core\Iviewred_ctl.java:46: cannot resolve symbol
symbol : constructor BIOlapFunction (java.lang.String,com.sapportals.guimachine.ep5kit.Iviewred_ctl,java.lang.String,java.lang.String,java.lang.String,int,int,java.lang.String)
location: class com.sap.portal.guimachine.bikit.runtime.BIOlapFunction
BIOlapFunction BIO1OZ = new BIOlapFunction ("BIO1OZ", this, profile.getProperty("System1"), "BIO_DEFAULT", "<Objects id=\"\" type=\"TEMPLATE_METADATA\"><Object id=\"0\" type=\"SCHEMA\" name=\"$INFOCUBE\"/><Object id=\"0\" type=\"CUBE\" name=\"$EMP_CUBE\"/><Object id=\"1\" type=\"MEASURE_DIMENSION\" name=\"Key Figures\" uniquename=\"[Measures]\"/></Objects><Objects id=\"\" type=\"TEMPLATE_PARAMETER\"><Object id=\"CUBE\" type=\"TEMPLATE_PARAMETER\" text=\"$EMP_CUBE\" value=\"$EMP_CUBE\" techname=\"null\" uniquename=\"null\"/><Object id=\"MEASURES\" type=\"TEMPLATE_PARAMETER\" text=\"[Measures].[SALARY]\" value=\"[Measures].[SALARY]\" techname=\"null\" uniquename=\"null\"/></Objects><Objects id=\"\" type=\"TEMPLATE_FILTER\"/>",2,500,"KEY");
^
1 error
can any one help us .
Thanking in advance.
Rajendra Redekar

We are having a similar issue. We have been able to deploy non-BI content on our setup. There seems to be a problem with the BI plugin piece.
Sequence:
1) Confirmation: PAR name may exceed OS limits. To avoid errors PAR was automatically renamed to: com.autogen.guimachine_0509145218.par
2)Error in executing a process for compilation, .\GUIMachine_Business_Packages\bw_query_wizard_model_53826\com.autogen.guimachine_0509145218\src.core\Iview_7k_ctl.java:46: cannot resolve symbol
symbol : constructor BIOlapFunction (java.lang.String,com.sapportals.guimachine.ep5kit.Iview_7k_ctl,java.lang.String,java.lang.String,java.lang.String,int,int,java.lang.String)
location: class com.sap.portal.guimachine.bikit.runtime.BIOlapFunction
BIOlapFunction BIO94 = new BIOlapFunction ("BIO94",
this, profile.getProperty("System1"), "RANKING_TOPN", "<Objects id=\"\" type=\"TEMPLATE_METADATA\"><Object id=\"0\" type=\"SCHEMA\" name=\"CO_C01\"/><Object id=\"0\" type=\"CUBE\" name=\"CO_C01/ZSEM_CO_C01_Q001\"/><Object id=\"1\" type=\"MEASURE_DIMENSION\" name=\"Key Figures\" uniquename=\"[Measures]\"/></Objects><Objects id=\"\" type=\"TEMPLATE_PARAMETER\"><Object id=\"TOPENABLED\" type=\"TEMPLATE_PARAMETER\" text=\"true\" value=\"true\" techname=\"null\" uniquename=\"null\"/><Object id=\"TOPRANKTYPE\" type=\"TEMPLATE_PARAMETER\" text=\"Count\" value=\"Count\" techname=\"null\" uniquename=\"null\"/><Object id=\"TOPVALUE\" type=\"TEMPLATE_PARAMETER\" text=\"5\" value=\"5\" techname=\"null\" uniquename=\"null\"/><Object id=\"BOTTOMENABLED\" type=\"TEMPLATE_PARAMETER\" text=\"false\" value=\"false\" techname=\"null\" uniquename=\"null\"/><Object id=\"BOTTOMRANKTYPE\" type=\"TEMPLATE_PARAMETER\" text=\"Percent\" value=\"Percent\" techname=\"null\" uniquename=\"null\"/><Object id=\"BOTTOMVALUE\" type=\"TEMPLATE_PARAMETER\" text=\"5\" value=\"5\" techname=\"null\" uniquename=\"null\"/><Object id=\"MEASURE\" type=\"TEMPLATE_PARAMETER\" text=\"Tons Billed\" value=\"[Measures].[3VK0EY29VB8ZFHGIZ6JT89G4R]\" techname=\"3VK0EY29VB8ZFHGIZ6JT89G4R\" uniquename=\"[Measures].[3VK0EY29VB8ZFHGIZ6JT89G4R]\"/><Object id=\"DIMENSION\" type=\"TEMPLATE_PARAMETER\" text=\"Sales Basis Weight\" value=\"[0MATERIAL__SLSBASWT]\" techname=\"0MATERIAL__SLSBASWT\" uniquename=\"[0MATERIAL__SLSBASWT]\"/><Object id=\"HIERARCHY\" type=\"TEMPLATE_PARAMETER\" text=\"Sales Basis Weight\" value=\"[0MATERIAL__SLSBASWT]\" techname=\"0MATERIAL__SLSBASWT\" uniquename=\"[0MATERIAL__SLSBASWT]\"/><Object id=\"LEVEL\" type=\"TEMPLATE_PARAMETER\" text=\"Sales Basis Weight Level 01\" value=\"[0MATERIAL__SLSBASWT].[LEVEL01]\" techname=\"LEVEL01\" uniquename=\"[0MATERIAL__SLSBASWT].[LEVEL01]\"/></Objects><Objects id=\"\" type=\"TEMPLATE_FILTER\"/>",2,500,"KEY");
1 error
It points specifically to "BIO94" in this line:
BIOlapFunction BIO94 = new BIOlapFunction ("BIO94"...
Any help is welcome.
Message was edited by: Jeff Tawater

Problems during deploy of an EAR with MDS enabled

I am trying to deploy an EAR with MDS enabled (file-repository) to a WLS cluster, but I get this error:
weblogic.application.ModuleException: :oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/xliffBundles" mapped to metadata-store-usage "MAR_TargetRepos" but its definition was not found in MDS configuration.
Why does it happen? What should I check/do to solve the problem?
Note that the deploy of the same EAR to the integrated WLS in Jdev works without exceptions.
Thanks
Edited by: user10047839 on 23-giu-2011 5.53

When i tried to deploy the application using Jdeveloper Deployment Wizard, it prompts me a popup for 'Deployment Configuration' where we need to specify Respository Name, Respository Type, Partition Name, path/JNDI Info. I selected proper values and deployed, the applcation is deployed perfectly and works fine.
But when i try to deploy the application using build.xml file, its error out as show below
weblogic.application.ModuleException: :oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/xliffBundles" mapped to metadata-store-usage "MAR_TargetRepos" but its definition was not found in MDS configuration.
I have provided the adf-config.xml below.
********************************adf-config.xml******************
<?xml version="1.0" encoding="windows-1252" ?>
<adf-config xmlns="http://xmlns.oracle.com/adf/config"
xmlns:adf="http://xmlns.oracle.com/adf/config/properties"
xmlns:sec="http://xmlns.oracle.com/adf/security/config">
<adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
<adf-property name="adfAppUID" value="Tenders-2723"/>
</adf:adf-properties-child>
<sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
<CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
<sec:JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
authorizationEnforce="true"
authenticationRequire="true"/>
</sec:adf-security-child>
<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
<mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
<cust-config>
<match path="/">
<customization-class name="oracle.adf.share.config.ADFUserCC"/>
</match>
</cust-config>
<persistence-config>
<metadata-namespaces>
<namespace path="/persdef" metadata-store-usage="MAR_TargetRepos"/>
</metadata-namespaces>
<metadata-store-usages>
<metadata-store-usage id="MAR_TargetRepos" deploy-target="true"
default-cust-store="true">
<metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
<property value="mds-ADF_MDS" name="repository-name"/>
<property value="jdbc/mds/ADF_MDS"
name="jndi-datasource"/>
<property value="TendersAviation" name="partition-name"/>
</metadata-store>
</metadata-store-usage>
</metadata-store-usages>
</persistence-config>
</mds-config>
</adf-mds-config>
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
<taglib-config>
<taglib uri="http://xmlns.oracle.com/adf/faces/rich">
<tag name="table">
<attribute name="filterVisible">
<persist-changes>
true
</persist-changes>
</attribute>
</tag>
<tag name="column">
<attribute name="displayIndex">
<persist-changes>
false
</persist-changes>
</attribute>
<attribute name="frozen">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="noWrap">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="selected">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="visible">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="width">
<persist-changes>
false
</persist-changes>
</attribute>
</tag>
<tag name="panelBox">
<attribute name="disclosed">
<persist-changes>
true
</persist-changes>
</attribute>
</tag>
<tag name="panelSplitter">
<attribute name="collapsed">
<persist-changes>
true
</persist-changes>
</attribute>
<attribute name="splitterPosition">
<persist-changes>
true
</persist-changes>
</attribute>
</tag>
</taglib>
</taglib-config>
<persistent-change-manager>
<persistent-change-manager-class>
oracle.adf.view.rich.change.MDSDocumentChangeManager
</persistent-change-manager-class>
</persistent-change-manager>
</adf-faces-config>
</adf-config>

Classpath problem during deployment in oracle 10g application server

java.lang.NoClassDefFoundError: oracle/toplink/sessions/UnitOfWork
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpApplication.loadServlet(HttpApplication.java:2028)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpApplication.findServlet(HttpApplication.java:4523)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2561)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:640)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:208)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:125)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
required urgent help.

hello,
when you deploy reports JSPs they still require the reports specific componentes (e.g. TLD file, classes, ...) etc be available. i doubt that's the case in your ear file.
thanks,
ph.

Problem During deployment

HI
PLease tell ur suggestions for this error:
I expected very soon
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
D:\jboss-4.0.0\server\default\work\jboss.web\localhost\sample\org\apache\jsp\index_jsp.java:59: handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext cannot be applied to (java.lang.Throwable)
if (_jspx_page_context != null) jspxpage_context.handlePageException(t);
^
1 error
     org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
     org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:332)
     org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:412)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:472)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs.
--------------------------------------------------------------------------------

It looks like jspxpage_context.handlePageException( t );
is expecting ' t ' in the above code to be of type java.lang.Exception.
Instead, its of type java.lang.Throwable. If you look up on the internet 'java.lang.Exception', you will see its derived (through inheritance) from java.lang.Throwable. Therefore you might be able to change your code from
jspxpage_context.handlePageException( t );
to
jspxpage_context.handlePageException( new java.lang.Exception(t) );
to elminate the error. This should work, but its not a good way to program. Instead, your JSP page should only display data and not have any business logic (such as your business logic in the JSP page that is throwing exceptions). If you read up on Model View Controller (MVC) you will see 'separation of concerns) about only using JSP to display data.
D:\jboss-4.0.0\server\default\work\jboss.web\localhost\sample\org\apache\jsp\index_jsp.java:59: handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext cannot be applied to (java.lang.Throwable)
if (_jspx_page_context != null) jspxpage_context.handlePageException(t);
I believe you need to import some java package into your JSP page.
Example of importing a package:
<%@ page import="java.util.*" %>
if (_jspx_page_context != null) jspxpage_context.handlePageException(t);
^
1 error

Getting problem during deploying desktop application with JNLP File.

Hi,
I am developing one standalone (desktop) application in swing. I want to make one jnlp file that would be install on my computer as a client(suppose). When i am doing jav web start enabled after that making application descriptor. But when i am running a web browser where i have stored my html file. but it is giving me an error that codebase or something like this. Please tell me is there any other way to do this task. Please help me to do this. Is NetBeans ide is best way to do this. please help me.
Thanks in advance.
Manveer.

>
...but it is giving me an error that codebase or something like this. ...>Try changing the JNLP file to 'something like that', that might work.
In case it does not, I provide a tool called JaNeLA that will provide a lot more specific error message(s) than 'something like this'.
Really, I cannot see you getting better help than on some of your other recent threads, with vague, unspecific error messages, and without putting the JNLP file and other relevant information.

"Program files" directory problem during Microsoft Office Customization Installer in non-English versions of Windows

We have a document-level customization solution for Word and are experiencing problems during deployment in an environment running on terminal services. The OS (Windows 2012) is English and Word (2013) is non-English (German).
Installation is done into the "Program Files" folder correctly. But when trying to start a word document linked to the specific template. The "Microsoft Office Customization Installer" pops up with the error.
"There was an error during installation"
From: file:///C:/Programme/[CompanyName]/[Productname]/[Productname].vsto
Downloading file:///c:/Programme/[CompanyName]/[Productname]/[Productname].vsto did not succeed.
Exception: ....
System.Deployment.Application.DeploymentDonwloadException: Download file:///C:/Programme/[Companyname]/Productname]/[Productname].vsto did not suceed. ---> System.Net.WebException: Could not find a part of the path 'C:\Programme\[Companyname]\[Productname]\[Productname].vsto'.
---> System.Net.WebException: ...... ---> System.IO.DirectoyNotFoundException......
The problem seems to be that the installer is looking for C:\PROGRAMME instead of C:\PROGRAM FILES. C:\PROGAMME is the German localized name of PROGRAM FILES (http://en.wikipedia.org/wiki/Program_Files).
The installer installs the solution correctly deployed into c:\program files, but when the later a user tries to start it and the Microsoft Office Customization Installer is called, it tries to access the non-existing "c:\programme" folder. This
doesn't exist, because Windows is English.
Is there any thing related to deploying solutions on a platform which has different languages (mixing/matching of OS language and Office language?)
Thank you for your help

Hello,
1. First, I would confirm with you whether you dealt with the localization for your document-level add-in?
2. Did you use this way to define the Create a class that defines the post-deployment action part of Put the document of a solution
onto the end user's computer (document-level customizations only) and did you get the path with Environment.SpecialFolder enum?
To handle this, I would recommend you consider using Environment.SpecialFolder to set that property.
Regards,
Carl
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Crystal Report not showing up during deployment for CRVS2010

Hi,
Have encountered problem when deploying Crystal Report using VB 2010. The report is able to show up during ASP.net development using VS 2010 but when i try to deploy on a IIS server, the report is just showing a blank page when trying to view using an Explorer on the client side. I'm using Window XP IIS 5.1 web server.
Have tried doing VB setup and installing the merge module CRruntime_13_0_1 but still not working.
Any help will be appreciated.
Thanks
KB

While the supported platform text says that Microsoft IIS5.1 is supported, I'm a bit dubious as CR 2008 (v. 12.x) did not support IIS5.1. See [KB 1494954 - Crystal Reports 2008 DHTML viewer for VS .NET is blank when displayed on a web form|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333433393334333933353334%7D.do].
I'll check with Program Management and get back with a definitive answer.
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

ClassCastException during deployment with more than one used entity

Hi,
i am still trying to get into NW development and got one more time stuck. I have a CE 7.1 SR5 project containing a dictionary, a bean module, an EAR project and a web dynpro project.
With the following two classes everything runs fine:
[AT]Entity
[AT]Table(name="TMP_USER")
[AT]NamedQueries(value={[AT]NamedQuery(name="doLogin", query="SELECT u FROM User u WHERE u.login = :login AND u.password = :password")})
public class User implements Serializable {
     [AT]Id
     private int id;
     private String login;
     private String password;
     private static final long serialVersionUID = 1L;
     public User() {
          super();
// Omitted Accessors
[AT]Stateless(name="UserSessionBean")
[AT]WebService
public class UserSessionBean implements UserSessionLocal
     [AT]PersistenceContext(unitName="DBAccess")
     private EntityManager em;
     public User doLogin(String login, String password)
          Query query = em.createNamedQuery("doLogin");
          query.setParameter("login", login);
          query.setParameter("password", password);
          try
               return (User) query.getSingleResult();
          catch(NoResultException e)
               return null;
build, deploy, run in webservice navigator -> ok
Then i created a new entity:
[AT]Entity
[AT]Table(name="TMP_PROJECT")
[AT]NamedQueries(value={[AT]NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
public class Project implements Serializable {
     [AT]Id
     private int id;
     private int ownerid;
     private String name;
     private Timestamp creationtime;
     private String description;
     private int number;
     private short subnumber;
     private static final long serialVersionUID = 1L;
     public Project() {
          super();
Omitted Accessors
build, deploy, run in webservice navigator -> no problem.
Then i changed the UserSessionBean to:
[AT]Stateless(name="UserSessionBean")
[AT]WebService
public class UserSessionBean implements UserSessionLocal
     [AT]PersistenceContext(unitName="DBAccess")
     private EntityManager em;
     public User doLogin(String login, String password)
          Query query = em.createNamedQuery("doLogin");
          query.setParameter("login", login);
          query.setParameter("password", password);
          try
               return (User) query.getSingleResult();
          catch(NoResultException e)
               return null;
     public Projecet testfunc()
          return null;
And now during deployment there is an warning (in reality it´s an exception) and the bean does not work any more.
The exception is
          1. Exception has been returned while the 'testproject.testcorp.de/testprojectear' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7707450:com.sap.engine.services.deploy.container.DeploymentException:
     at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:693)
     at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
     at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
     at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
     at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occured during web services deployment. Unable to generate serialization framework for web service UserSessionBeanService, application testproject.testcorp.de/testprojectear.
     at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:360)
     at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:220)
     at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.execute(WSInitialStartProcess.java:140)
     at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:316)
     at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:688)
     ... 37 more
Caused by: java.lang.ClassCastException: class com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive incompatible with class com.sun.xml.bind.v2.model.impl.ClassInfoImpl:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive
     at com.sun.xml.bind.v2.model.impl.ClassInfoImpl.getBaseClass(ClassInfoImpl.java:170)
     at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:58)
     at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:38)
     at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:142)
     at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
     at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
     at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
     at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
     at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
     at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
     at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
     at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
     at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
     at java.util.AbstractList$Itr.next(AbstractList.java:422)
     at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
     at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
     at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
     at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
     at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
     at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
     at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
     at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
     at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
     at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
     at java.util.AbstractList$Itr.next(AbstractList.java:422)
     at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
     at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
     at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
     at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
     at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:204)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:356)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:217)
     at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
     at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
     at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
     at com.sap.engine.services.webservices.jaxws.j2w.JaxWsSchemaGenerator.genJaxbMappings(JaxWsSchemaGenerator.java:274)
     at com.sap.engine.services.webservices.jaxws.j2w.JaxWsIMappingGenerator.generateWSDL(JaxWsIMappingGenerator.java:103)
     at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:286)
     ... 41 more
I already downgraded my Java JRE/JDK to 1.5.0_15 as it was hinted here in the forum, but the problem persists. Any idea what is wrong?

Thanks for the answer, but i am not using this wizard. Some how this project class must be flawed.
public User testfunc()
return null;
works, but changing to
public Project testfunc()
return null;
immediately leads to the above deployment error.
This is the offending class, it compiles without warning
package de.testcorp.testproject.beans;
import java.io.Serializable;
import java.sql.Timestamp;
import javax.persistence.*;
@Entity
@Table(name="TMP_PROJECT")
@NamedQueries(value={@NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
public class Project implements Serializable {
     @Id
     private int id;
     private int ownerid;
     private String name;
     private Timestamp creationtime;
     private String description;
     private int number;
     private short subnumber;
     private static final long serialVersionUID = 1L;
     public Project() {
          super();
     public int getId() {
          return this.id;
     public void setId(int id) {
          this.id = id;
     public int getOwnerid() {
          return this.ownerid;
     public void setOwnerid(int ownerid) {
          this.ownerid = ownerid;
     public String getName() {
          return this.name;
     public void setName(String name) {
          this.name = name;
     public Timestamp getCreationtime() {
          return this.creationtime;
     public void setCreationtime(Timestamp creationtime) {
          this.creationtime = creationtime;
     public String getDescription() {
          return this.description;
     public void setDescription(String description) {
          this.description = description;
     public int getNumber() {
          return this.number;
     public void setNumber(int number) {
          this.number = number;
     public short getSubnumber() {
          return this.subnumber;
     public void setSubnumber(short subnumber) {
          this.subnumber = subnumber;

Error during deployment of Message Driven Bean

Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          I am getting some error (or perhaps warning) during deployment of Message
          Driven Bean. Any one seen this before?
          This error only comes on a machine with Dual Network card.
          Thanks.
          ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
          <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
          enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
          Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
          is of a non-final version of the appropriate specification. It is subject to
          change in future releases once the specification becomes finalized. This may
          cause application code developed for BEA WebLogic Server 6.1 that uses the
          new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          supported in future releases of BEA WebLogic Server.>
          ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          container will automatically attempt to re-establish the connection with the
          JMS server. This warning may occur during WebLogic Cluster start-up if the
          JMS destination is located on another server. When the JMS server connection
          is re-established, the Message-Driven EJB will again receive JMS messages.
          The Error was:
          Unable to create a JNDI InitialContext to lookup the JMS destination. The
          error was:
          javax.naming.CommunicationException. Root exception is
          java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          nested exception is:
          java.net.ConnectException: Connection refused: connect; No available router
          to destination
          at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:307)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:211)
          at
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          ory.java:149)
          at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          at javax.naming.InitialContext.init(InitialContext.java:217)
          at javax.naming.InitialContext.<init>(InitialContext.java:193)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          rivenBeanInfoImpl.java:641)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          nPoller.java:474)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          .java:418)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          nectionPoller.java:286)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          foImpl.java:511)
          at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          at weblogic.j2ee.Application.addComponent(Application.java:170)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          arget.java:360)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          Target.java:285)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          eploymentTarget.java:239)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          entTarget.java:199)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy34.updateDeployments(Unknown Source)
          at
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          ServerMBean_CachingStub.java:2977)
          at
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          icationManager.java:372)
          at
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          r.java:160)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy49.start(Unknown Source)
          at
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          ApplicationManagerMBean_CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          at weblogic.management.Admin.finish(Admin.java:644)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          at weblogic.Server.main(Server.java:35)
          >
          ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010009> <EJB Deployed EJB with JNDI name
          ASYNCMessageDrivenBean.>


Hi Tom
          Yes we do have an URL provided in the descriptor. It's
          t3://jms.server.net:7001.
          and the jms.server.net is resolved via a hosts file in Win2K
          eg,
          192.168.100.200 jms.server.net
          You are right in saying that the loopback in a dual-net card is a problem.
          But our solution
          above solves the issue as long as your host file does not use 127.0.0.1 as
          the IP.
          We need the URL b/c depending on our client's deployment , the JMS Server
          may be remote or may be local.
          "Tom Barnes" <[email protected]> wrote in message
          news:[email protected]...
          > Hi x,
          >
          > Something to do with the loopback and dual-network cards is
          > messin' with WLS' mind. I do not know what the problem is,
          > but I can guess:
          >
          > You have specified an URL in the MDB descriptor when there
          > is no need for one. If t3://127.0.0.1:7001 is in the same
          > cluster the MDB is running in (I suspect this URL is
          > actually the same WL server), then don't specify the URL.
          > This URL is only useful for connecting an MDB to a JMS
          > server that is outside local server and outside the cluster.
          > The URL may be working on single-network card systems
          > as perhaps then WL has enough info to guess that you
          > actually mean the local WL server, and simply converts
          > the context to a local context.
          >
          > Note that the URL option in the MDB descriptor is actually
          > a WebLogic extension of J2EE.
          >
          > Tom
          >
          >
          >
          > x wrote:
          > > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          > >
          > > I am getting some error (or perhaps warning) during deployment of
          Message
          > > Driven Bean. Any one seen this before?
          > > This error only comes on a machine with Dual Network card.
          > >
          > > Thanks.
          > >
          > >
          > >
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
          features
          > > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
          1.2,
          > > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
          6.1
          > > is of a non-final version of the appropriate specification. It is
          subject to
          > > change in future releases once the specification becomes finalized. This
          may
          > > cause application code developed for BEA WebLogic Server 6.1 that uses
          the
          > > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          > > supported in future releases of BEA WebLogic Server.>
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          > > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          > > container will automatically attempt to re-establish the connection with
          the
          > > JMS server. This warning may occur during WebLogic Cluster start-up if
          the
          > > JMS destination is located on another server. When the JMS server
          connection
          > > is re-established, the Message-Driven EJB will again receive JMS
          messages.
          > > The Error was:
          > > Unable to create a JNDI InitialContext to lookup the JMS destination.
          The
          > > error was:
          > > javax.naming.CommunicationException. Root exception is
          > > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          > > nested exception is:
          > > java.net.ConnectException: Connection refused: connect; No available
          router
          > > to destination
          > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:307)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:211)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          > > ory.java:149)
          > > at
          javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          > > at
          javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          > > at javax.naming.InitialContext.init(InitialContext.java:217)
          > > at javax.naming.InitialContext.<init>(InitialContext.java:193)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          > > rivenBeanInfoImpl.java:641)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          > > nPoller.java:474)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          > > .java:418)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          > > nectionPoller.java:286)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          > > foImpl.java:511)
          > > at
          weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          > > at weblogic.j2ee.Application.addComponent(Application.java:170)
          > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          > > arget.java:360)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          > > Target.java:285)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          > > eploymentTarget.java:239)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          > > entTarget.java:199)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy34.updateDeployments(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          > > ServerMBean_CachingStub.java:2977)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          > > icationManager.java:372)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          > > r.java:160)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy49.start(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          > > ApplicationManagerMBean_CachingStub.java:480)
          > > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          > > at weblogic.management.Admin.finish(Admin.java:644)
          > > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          > > at weblogic.Server.main(Server.java:35)
          > >
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010009> <EJB Deployed EJB with JNDI name
          > > ASYNCMessageDrivenBean.>
          > >
          > >
          >

Problem during installation of NW7.0 SR3 on Windows x64

Hello all,
I have a problem during the installation of a new central instance.
During the phase 38 "Install Software units", SAPINST shows that logs :
Jul 30, 2008 1:41:10 PM Info: Ending deployment prerequisites. All items are correct.
Jul 30, 2008 1:41:11 PM Info: Saved current Engine state.
Jul 30, 2008 1:41:11 PM Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/model/eap'/'sap.com'/'MAIN_APL70VAL_C'/'1497904'/'5' will be deployed.
Jul 30, 2008 1:41:11 PM Info: SDA to be deployed: D:\usr\sap\PAD\DVEBMGS00\SDM\root\origin\sap.com\caf\eu\gp\model\eap\MAIN_APL70VAL_C\5\1497904\cafeugpmodeleap.sda
Jul 30, 2008 1:41:11 PM Info: Software type of SDA: J2EE
Jul 30, 2008 1:41:11 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 30, 2008 1:41:13 PM Info: Begin of log messages of the target system:
08/07/30 13:41:11 - ***********************************************************
08/07/30 13:41:12 - Start updating EAR file...
08/07/30 13:41:12 - start-up mode is lazy
08/07/30 13:41:12 - EAR file updated successfully for 250ms.
08/07/30 13:41:12 - Start deploying ...
08/07/30 13:41:12 - EAR file uploaded to server for 93ms.
08/07/30 13:41:13 - ERROR: NOT deployed. The Deploy Service returned the following error:
                     For detailed information see the log file of the Deploy Service.
                     Exception is:
                     com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
                          Nested exception is:
                          java.net.SocketException: Connection reset
                     java.net.SocketException: Connection reset
                          at java.net.SocketInputStream.read(SocketInputStream.java:168)
                          at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:395)
                          at java.lang.Thread.run(Thread.java:534)
08/07/30 13:41:13 - ***********************************************************
Jul 30, 2008 1:41:13 PM Info: End of log messages of the target system.
Jul 30, 2008 1:41:13 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 30, 2008 1:41:13 PM Error: Aborted: development component 'caf/eu/gp/model/eap'/'sap.com'/'MAIN_APL70VAL_C'/'1497904'/'5', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'5':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
     Nested exception is:
     java.net.SocketException: Connection reset
Exception is:
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
     Nested exception is:
     java.net.SocketException: Connection reset
java.net.SocketException: Connection reset
     at java.net.SocketInputStream.read(SocketInputStream.java:168)
     at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:395)
     at java.lang.Thread.run(Thread.java:534)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Jul 30, 2008 1:41:13 PM Info: Starting to save the repository
Jul 30, 2008 1:41:13 PM Info: Finished saving the repository
What can I do to validate that step ?
Thanks in advance,
Edited by: Alexandre Belgrand on Jul 30, 2008 1:48 PM

Hi,
I had same problem.i resolved it by reinstalling OS and configuring high Page file.
Please set the max and min Page file size of same value.
and also do the java memory tuning as per SAP Notes.
Regards,
Sandeep Nayak

Error during deployment - SOA Suite 11.1.1.4.0

Hi,
When I try to deploy bpel flow in the SOA Suite 11.1.1.4.0 i receive the error below:
The bpel flow deploy and works fine in the SOA Suite 11.1.1.3.0_ (Jdeveloper 11.1.1.3.0)
#;There was an error deploying the composite on AdminServer: Deployment Failed: Error occurred during deployment of component: CllReceiveEmployeeFromPSFTEBS to service engine: implementation.bpel, for composite: cll_ReceiveEmployeeFromPSFT: ORABPEL-05250
#;Error deploying BPEL suitcase.
#;error while attempting to deploy the BPEL component file "/vol02/appsoa/product/11.1.0/user_projects/domains/base_domain/servers/AdminServer/dc/soa_5d9300f2-10a2-4784-8865-83f7159ee9ce"; the exception reported is: java.lang.Exception: BPEL 1.1 compilation failed
#;This error contained an exception thrown by the underlying deployment module.
#;Verify the exception trace in the log (with logging level set to debug mode).
[04:07:33 PM] Check server log for more details.
[04:07:33 PM] Error deploying archive sca_CllReceiveEmployeeFromPSFT_rev1_0.jar to partition "ebs_psft" on server AdminServer [brdell21.br.oracle.com:7001]
[04:07:33 PM] #### Deployment incomplete. ####
[04:07:33 PM] Error deploying archive file:/C:/jdev11g/mywork/EBS-PSFT/CllReceiveEmployeeFromPSFT/deploy/sca_CllReceiveEmployeeFromPSFT_rev1_0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Regards,
Marcos Allonso

Hi,
I copied fle sca_cll_ReceiveEmployeeBankAccountFromPSFT_rev1_0.jar to C:\jdev11g\mywork\EBS-PSFT\CllReceiveEmployeeBankAccountFromPSFT\SCA-INF\lib , redeploy flow but the problem remain.
*** I am using a Jdeveloper 11.1.1.3.0 to deploy flow in the SOA Suite 11.1.1.4.0
Regars,
Marcos

Org.xml.sax.SAXParseException during deploying project in SOA 11G

Hello,
I was migrating a project from SOA 10G to SOA 11G (11.1.1.3). I had to make a few changes in the project such as:
1) Put concrete wsdl's
2) Put "<bpelx:exec import="oracle.soa.common.util.Base64Decoder"/>" in the bpel file
3) Change the database adapters to have "toplink" as the persistence provider as when I migrated the file , it changed it to Eclipse
4) Fill in the port and location in the reference portion of the composite.xml
At the end of all these changes , my project compiled properly , but when I tried to deploy it , I am getting this error:
[09:57:27 AM] Error deploying archive sca_MIA_ModuleInvToGP_rev1.0.jar to partition "default" on server soa_server1 [sv-soafm-dev1.infinera.com:8001]
[09:57:27 AM] HTTP error code returned [500]
[09:57:27 AM] Error message from server:
Error during deployment: org.xml.sax.SAXParseException: <Line 26, Column 68>: XML-20221: (Fatal Error) Invalid char in text.: <Line 26, Column 68>: XML-20221: (Fatal Error) Invalid char in text..
[09:57:27 AM] Check server log for more details.
I am unable to know where this particular error is coming from , and do not know how to resolve this. Does any one have any idea on what could be the possible reason for this?
Seems to be a problem with some XML file , but I dont know which file to check.
Any help is welcome.
Thanks
Manan Sanghvi

In the session.xml schema it is a choice between driver-class/url and datasource, so you need to remove the driver-class tag as you are using a datasource.
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<datasource>jdbc/AlfaDS</datasource>
replalce with,
<datasource>jdbc/AlfaDS</datasource>

DTD not available during deployment

Hello
We had a problem that during the deployment of our ear, some dtd's of struts where not accessible on the internet. It seems that xml files are validated, during deployment, so the application was not deployed properly.
Is there a way to either :
- configure the container that no validatio should be done when deploying the ear
- put the dtd in the application itself, so we don't depend on the struts site wether we can deploy or not
grtz
Chris.

The problem is I am trying to use JavaMail in an EJB and it gives me the error if I create a javax.mail.Session. If I comment out the Session, deployment is fine. I am thinking that maybe the problem is I am using 8i version 8.1.5 and it only supports java 1.1.8.

Problem during deploying

Similar Messages

Maybe you are looking for