Deployment problems on AIX
Hi!
I have a connector and a demo setup to exercise it, using a Servlet and an EJB
to access the connector. This works flawlessly under NT 4.0. When I try to deploy
the same thing under AIX 4.3 everything seems to work smoothly, i.e. the connector
starts and creates an initial ManagedConnection (I can see it from the logs),
the EJB deploys without errors, and JNDI names are properly entered. But when
I try to run the servlet I get the initial page, then when I try to send data
to the EJB I get the following exception. Any idea what's causing this? I've never
seen this on NT.
javax.resource.ResourceException: Problem granting connection request to a Manag
edConnectionFactory which does not exist in connection pool. Check your MCF's
ha
shcode()
at java.lang.Exception.<init>(Exception.java:44)
at javax.resource.ResourceException.<init>(ResourceException.java:73)
at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
n(ConnectionPoolManager.java:133)
at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
ection(ConnectionManagerImpl.java:20)
at no.gar.connector.api.GarConnectionFactory.getConnection(Unknown Sourc
e)
at no.gar.distrib.DistribEJB.getCCIConnection(DistribEJB.java:265)
at no.gar.distrib.DistribEJB.execute(DistribEJB.java:169)
at no.gar.distrib.DistribEJBImpl.execute(DistribEJBImpl.java:110)
at no.gar.distrib.DistribEJBEOImpl.execute(DistribEJBEOImpl.java:31)
at no.gar.distrib.DistribEJBEOImpl_WLSkel.invoke(DistribEJBEOImpl_WLSkel
.java:108)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
va:373)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
va:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
andler.java:118)
at weblogic.rmi.internal.BasicRequestDispatcher.dispatch(BasicRequestDis
patcher.java:115)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:
88)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:10
8)
at no.gar.distrib.DistribEJBEOImpl_WLStub.execute(DistribEJBEOImpl_WLStu
b.java:309)
at no.gar.distrib.DistribServlet.doGet(DistribServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:213)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:1265)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:1622)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
java.lang.NullPointerException
at no.gar.distrib.DistribEJB.execute(DistribEJB.java:170)
at no.gar.distrib.DistribEJBImpl.execute(DistribEJBImpl.java:110)
at no.gar.distrib.DistribEJBEOImpl.execute(DistribEJBEOImpl.java:31)
at no.gar.distrib.DistribEJBEOImpl_WLSkel.invoke(DistribEJBEOImpl_WLSkel
.java:108)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
va:373)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
va:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
andler.java:118)
at weblogic.rmi.internal.BasicRequestDispatcher.dispatch(BasicRequestDis
patcher.java:115)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:
88)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:10
8)
at no.gar.distrib.DistribEJBEOImpl_WLStub.execute(DistribEJBEOImpl_WLStu
b.java:309)
at no.gar.distrib.DistribServlet.doGet(DistribServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:213)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:1265)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:1622)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
TopLink requires reflective access to run. It is possible you need to configure your java policy file with the following permission for TopLink and the applications that use it.
//grant permission for OracleAS TopLink to use reflection
permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
Similar Messages
-
RE: [iPlanet-JATO] Re: Deployment problem
Chidu,
I think that you are mired in the very common confusion of the default
behavior of the ApplicationServletBase.parsePathInfo() which will determine
the controlling/handling ViewBean via a URL design pattern. Lets take a look
at the URL
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
is decomposed as follows:
/NASApp -> well, this is long story but is absolutely necessary, welcome to
iAS
/MigtoolboxSampleAppWar -> is the web application name, taken as the name of
the WAR file when there is no EAR file (this allows the Servlet/JSP
container to deferences the web application root under
<ias>/APPS/modules/MigtoolboxSampleAppWar) I think this part of the URL is
called th Context Path
/MigtoolboxSample -> is the Servlet Path, and will either directly reference
or match a Servlet Mapping
for instance
<servlet-mapping>
<servlet-name>MigtoolboxSampleServlet</servlet-name>
<url-pattern>/MigtoolboxSample/*</url-pattern>
</servlet-mapping>
tells the Servlet Container that the Servlet Path
/MigtoolboxSample
maps to the Module Servlet MigtoolboxSampleServlet
This is how EVERY request makes its way to the "front controller" pattern in
JATO. It is fundamental to JATO Applicatioan that every request pass
through the ModuleServlet.
every else on the URL past the Servlet Path is the PATH INFO. Based on this
understanding, you will see why the
ApplicationServletBase.parsePathInfo()
is so important. In parsePathInfo() the PATH INFO is compared to the design
pattern
/VIEWBEANNAME*
to determine the handling ViewBean from the first String Token in the path
info. For instance, the starting URL of the Sample Application is
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage
The PATH INFO is [IndexPage]
and IndexPage[ViewBean] is the handling ViewBean. Therefore, any simiarl
URL like
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.matt
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.mike
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.chidu
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.XXX
will all result in the same handling View Bean
IndexPageViewBean
It is very important to understand that you CANNOT hit the JATO JSPs
directly. You must hit the "front controller" ModuleServlet which will
always delegate control to the handling ViewBean (a la, the "service to
workers" pattern)
You can attempt to hit the JSP directly but you need the right J2EE URL
/NASApp/MigtoolboxSampleAppWar/MigtoolboxSampleApp/MigtoolboxSample/IndexPag
e.jsp
this URL will directly hit the JSP. However, you will recieve an error
because the JATO framework quickly determines that there is no
RequestContext in the HttpRequest attributes and assumes that the "front
controller" was bypassed. Try it. You will get ERROR.
Lets go back to what you are trying to do, place Models and Viewbeans in
separate directories. I recommend that you move the Models. Models are
ONLY referenced by TYPE via the ModelManager, the compiler will ensure that
your code is correct and matches the packages, file locations, import
statements, etc. ViewBeans, on the other hand are related to the
ModuleServlet their are contained in and are loaded via type names according
to a design pattern.
if you want to separate models and Viewbean then simply move the Model and
make sure everything compiles.
you cannot move the ViewBeans
if you do want to move the JSP peers of the Viewbeans, then you can put them
anywhere in the web application doc root. When you do, update the
DEFAULT_DISPLAY_URL as Mike suggested
matt
-----Original Message-----
From: Mike Frisino [mailto:<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217193234150166091061">Michael.Frisino@S...</a>]
Sent: Thursday, July 26, 2001 10:48 PM
Subject: Re: [iPlanet-JATO] Re: Deployment problem
Chidu,
Did you have it running fine in the original default configuration, before
you started changing things around? The URL should not access the .jsp
directly. The URL should look more like this
"/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage", without the
.jsp.
Also, please read the "Migration Tech Notes" document that is
linked to the
main doc index page. There is some information in there related
to trying to
run the sample application under iAS (see Tech Note 4 in
particular, "Note
on running the iMT "MigtoolboxSample" in iPlanet Application Server )
----- Original Message -----
From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164140244063078048234051197">chidusv@y...</a>>
Sent: Thursday, July 26, 2001 7:27 PM
Subject: [iPlanet-JATO] Re: Deployment problem
Hi Mike,
I tried changing the url in all the viewbeans to reflect the new sub-
directory for the viewbeans(I have placed the jsps and viewbeans in
a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
still not able to get access to the jsps. I basically see the
message "GX Error Socket Error Code missing!!" error on the browser
thrown by iPlanet, but the log doesn't tell me anything. Does the url
which I give to access the jsp change accordingly, i.e., should I
give something other
than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
If I try to use any other url other
than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
see the FileNotFoundException in the log.
I guess I'm still missing something.
Thanks for your help.
--Chidu.
--- In <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166136158139046209">iPlanet-JATO@y...</a>, "Mike Frisino" <<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217130152150">Michael.Frisino@S...</a>> wrote:
Chidu.
Did you also adjust the following member in each of the ViewBeans?
public static final String DEFAULT_DISPLAY_URL=
"/jatosample/module1/Index.jsp";
Try adjusting this to be consistent with your new hierarchy.
Also, if you still have problems, send us the error message thatyou recieve
when you try to access the page. That would help.
----- Original Message -----
From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164036129208">chidusv@y...</a>>
Sent: Thursday, July 26, 2001 4:48 PM
Subject: [iPlanet-JATO] Deployment problem
Hi,
We have a requirement to seperate the models and viewbeans and
keep
them in seperate directories. Is it possible to seperate the
viewbeans and models not be in the same directory?
I tried seperating the two in the MigtoolboxSampleApp application
provided by JATO. I changed the package and import statements
accordingly in the viewbeans, jsps and the models. But when I
deployed the application, I'm not able to access the Index page or
any of the jsps. Does the ApplicationServletBase always look forthe
viewbean in the same path as that of the module servlet?
Any help will be appreciated.
Thanks,
Chidu.
<a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
<a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
<a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>Hi Mike,
I tried changing the url in all the viewbeans to reflect the new sub-
directory for the viewbeans(I have placed the jsps and viewbeans in
a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
still not able to get access to the jsps. I basically see the
message "GX Error Socket Error Code missing!!" error on the browser
thrown by iPlanet, but the log doesn't tell me anything. Does the url
which I give to access the jsp change accordingly, i.e., should I
give something other
than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
If I try to use any other url other
than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
see the FileNotFoundException in the log.
I guess I'm still missing something.
Thanks for your help.
--Chidu.
--- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
>
Chidu.
Did you also adjust the following member in each of the ViewBeans?
public static final String DEFAULT_DISPLAY_URL=
"/jatosample/module1/Index.jsp";
Try adjusting this to be consistent with your new hierarchy.
Also, if you still have problems, send us the error message that you recieve
when you try to access the page. That would help.
----- Original Message -----
From: <chidusv@y...>
Sent: Thursday, July 26, 2001 4:48 PM
Subject: [iPlanet-JATO] Deployment problem
Hi,
We have a requirement to seperate the models and viewbeans and
keep
them in seperate directories. Is it possible to seperate the
viewbeans and models not be in the same directory?
I tried seperating the two in the MigtoolboxSampleApp application
provided by JATO. I changed the package and import statements
accordingly in the viewbeans, jsps and the models. But when I
deployed the application, I'm not able to access the Index page or
any of the jsps. Does the ApplicationServletBase always look for the
viewbean in the same path as that of the module servlet?
Any help will be appreciated.
Thanks,
Chidu.
[email protected] -
Web service proxy take ~4 minutes to detect connection problem in AIX!
Dear All,
i am developing a client application that consume web service , by jdeveloper 10.1.3.1.
i found a problem, in AIX, that the web service proxy generated by jdeveloper take long time
to detect connection problem to the server (e.g. server is down, network down, invalid
ip address or port supplied).
in ms window, if the proxy can't reach the server, it throw exception within seconds.
but in ibm AIX, it take about 4 minutes !!! the time is too long until the exception is thrown.
could anybody help me?
is there something i can set to greatly shorten the hanging time when connection
problem?
thank you.nobody experience this problem?
-
Deployment Problems of Enterprise Application in NWDS 7.1
Hello Everyone,<br>
<br>
I am having a problem when trying to deploy an application I made to the server. The project consists of two DCs, one which is an Enterprise Application and the other is a Web Module. I have configured the web module to be a dependency of the Enterprise application, so that the .war file generated from the Web Module DC is contained within the .ear file created when the Enterprise Application DC is built. The only dependency that the Web Module DC has is "engine.jee5.facade," which is there by default when it is created. I have not added any code to either DC, because I was just trying to test if I could deploy something to the server before I got into that. When I build the Enterprise Application DC, both DCs build successfully (because of the dependency). When I deploy the Enterprise Application DC, I get an "[ERROR CODE DPL.DC.5089]" error message. When I checked the SDN for what that error code means, I get sent to <a href="http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58">http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58</a>, which is pretty vague.
I did try to see if I could deploy the .ear by itself, without the war file within it (by removing the dependency on the Enterprise Application DC) and that seemed to work ok. Its just seems to be when the Web Module is a dependency of the Enterprise Application is when it fails. I have included the error message I get from NWDS below. Thanks in advance for any help you can offer. <br> <br> SUMMARY<br>
~~~~~~~~~~~~~~~~~~~<br>
Successfully deployed: 0<br>
Deployed with warnings: 0<br>
Failed deployments: 1<br>
~~~~~~~~~~~~~~~~~~~<br>
ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it. <br>
<br>
1. File:C:\Develop\workspace.jdi\2\DCs\sap.com\test\sgj_ent_app_test_three\_comp\gen\default\deploy\sap.comtestsgj_ent_app_test_three.ear<br>
Name:test~sgj_ent_app_test_three<br>
Vendor:sap.com<br>
Location:PDI_J2EETST1_D<br>
Version:20100716152020<br>
Deploy status:Aborted<br>
Version:HIGHER<br>
<br>
Description:<br>
1. [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.<br>
<br>
Exception:<br>
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:222)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:81)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:426)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
... 11 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:496)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
... 12 more
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException:
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:73)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:54)
at com.sap.engine.services.security.server.AuthenticationContextImpl.setProperty(AuthenticationContextImpl.java:533)
at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.initSecurityConfiguration(SecurityUtils.java:722)
at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.createSecurityResources(SecurityUtils.java:143)
at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.initXmls(DeployAction.java:778)
at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:301)
at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:340)
at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:341)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Edited by: Savin on Aug 5, 2010 10:25 PM
Edited by: Savin on Aug 5, 2010 10:26 PM
Edited by: Savin on Aug 5, 2010 10:31 PM
Edited by: Savin on Aug 5, 2010 5:27 PM
Edited by: Savin on Aug 5, 2010 5:38 PM
Edited by: Savin on Aug 5, 2010 5:44 PMHi Veera/Abhi
I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
On my NWDS PDA Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
2009-02-11 13:02:40 ... (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
Madhu--
Please find my ans to the following points mentioned by you
1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
It is assigned
2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
Rule is activated
3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
Rule is activated
4) Make sure that you have installed the following components in the following sequence in the PDA
- Creme
- MinDB/DB2e
- PDA_eswt_container
- PDA Runtime.
Client is installed in this sequence only. I referrred to help.sap.com while installing
the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking up the data. giving the above mentioned error.
Regards
Priya -
Message Driven Bean deployment problem in SAILFIN b12
Hi,
I am a fresh learner in EJB technology and have been experiencing a deployment problem while attempting to deploy a very simple message driven bean, that does nothing basically, to a SAILFIN (b12) application server instance. I am using NetBeans 5.5.1 to form the message driven bean but I deploy the bean manually on a Linux terminal. The following is the code of the bean:
package trial.mdb;
import javax.annotation.Resource;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.Message;
import javax.jms.MessageListener;
@MessageDriven(mappedName = "jms/MDB1", activationConfig = {
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
public class MDB1 implements MessageListener {
/** Creates a new instance of MDB1 */
public MDB1() {
public void onMessage(Message message) {
I got the following message after deployment attempt:
"Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [TrialMDB]. Please refer to the server log for more details."
The verifier does not give any error, warning or failure message and it states "com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;" in the server log. Below, I have stated the content of the server log. I am novice in EJB technology particularly in message driven beans so any help will be appreciated. Thanks a lot in advance.
--faydemir
The content of the server log:
[#|2008-01-02T16:25:11.106+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;|Verifying: [ _home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_TrialMDB ]|#]
[#|2008-01-02T16:25:11.286+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;_RequestID=c8eac819-597f-454b-b189-1ad5a88770ac;|
STATIC VERIFICATION RESULTS
NUMBER OF FAILURES/WARNINGS/ERRORS
# of Failures : 0
# of Warnings : 0
# of Errors : 0
END OF STATIC VERIFICATION RESULTS
|#]
[#|2008-01-02T16:25:11.286+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;|No errors found in the archive.|#]
[#|2008-01-02T16:25:11.367+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread-41;|deployed with moduleid = TrialMDB|#]
[#|2008-01-02T16:25:11.441+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=24;_ThreadName=Thread-40;MDB1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|MDB00017: [MDB1]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1]|#]
[#|2008-01-02T16:25:11.441+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|com.sun.enterprise.connectors.ConnectorRuntimeException
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
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:597)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:154)
at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:535)
at java.lang.Thread.run(Thread.java:619)
|#]
[#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=Thread-40;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1]|#]
[#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|appId=TrialMDB moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_TrialMDB ejbName=MDB1|#]
[#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|LDR5004: UnExpected error occured while creating ejb container
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
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:597)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:154)
at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:535)
at java.lang.Thread.run(Thread.java:619)
|#]
[#|2008-01-02T16:25:11.445+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|CORE5020: Error while loading ejb module|#]
[#|2008-01-02T16:25:11.446+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=24;_ThreadName=Thread-40;Error while loading EJB module [TrialMDB]. Please refer to the server log for more details. ;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|ADM1075:Error on listening event:[Error while loading EJB module [TrialMDB]. Please refer to the server log for more details. ]|#]Hi thank you for your answer. I did not create any jms resource in the application server because my message driven bean was not implementing the MessageListener interface. Since it did not work in that way, I added the MessageListenerInterface to the bean and formed the necessary jms resources usuing the admin console of the SAILFIN but it keeps giving the same message both on the linux terminal and the server log.
Let me explain my situation in a more detailed way. I am developing a JCA based resource adapter (i.e.) connector. The inbound module of the connector listens on a specific port for incoming messages from a server (EIS). The port property is defined in the connector's deployment descriptor. When a message reaches, the connector delivers it to the a message driven bean whose code is indicated in the following:
package com....;
import com....ra.facade.InboundListener;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.Message;
import javax.jms.MessageListener;
import java.util.logging.*;
* Entity class InboundMessageReceiverMDB
* @author efikayd
@MessageDriven(
mappedName = "InboundMessageReceiverMDB",
messageListenerInterface = com......ra.facade.InboundListener.class,
activationConfig = {
@ActivationConfigProperty(
propertyName = "listenerPort", propertyValue = "12345"),
@ActivationConfigProperty(
propertyName="ConnectionFactoryJndiName", propertyValue="RAjms/MyQCF"),
@ActivationConfigProperty(
propertyName="DestinationName", propertyValue="MyQueue"),
@ActivationConfigProperty(
propertyName="DestinationType", propertyValue="javax.jms.Queue")
public class InboundMessageReceiverMDB implements InboundListener, MessageListener {
private static final Logger logger = Logger.getLogger("com.xyz.inbound.InboundMessageReceiverMDB");
/** Creates a new instance of InboundMessageReceiverMDB */
public InboundMessageReceiverMDB() {
public void onMessage(Message message) {
public void receiveMessage(String message) {
logger.log(Level.SEVERE, "CLASS: " + getClass().getName() + "METHOD: receiveMessage() ==> Message received...: " + message);
The listener interface is the following:
package com...ra.facade;
public interface InboundListener{
public void receiveMessage(String message);
I have set the JMS resource and the destination resource properties on the admin console in the following manner:
ConnectionFactory:
JNDI Name: RAjms/MyQCF
Pool Name: RAjms/MyQCF
Type: javax.jms.ConnectionFactory
Status: enabled
Property1 ==> Name: DestinationType Value: javax.jms.Queue
Property2 ==> Name: DestinationName Value: MyQueue
Destination (i.e. queue):
JNDIName: MyQueue
Physical Destination Name: MyQueue
status: enabled
Property1 ==> Name: DestinationType Value:javax.jms.Queue
Property2 ==> Name: DestinationName Value:MyQueue
Although I created the JMS resources as above I am getting the same problems.Do you think the above configuration is fine and appropriate to the activation configuration definitions in my message driven bean code? Am I missing something on this configuration? Below, I have indicated the message that I got on the linux terminal when I attempt to deploy the message driven bean and the related server log. They are same as what I posted before (i.e. JMS resource cannot be created...). Thank you very much in advance for your help.
Kind regards,
faydemir
PS: The 'restart' command in the following linux terminal outcome basically makes a call to a bash script which deploys the message driven bean to the SAILFIN application server. The resource adapter instance is already deployed on the application server before attempting to deploy the message driven bean.
WHILE DEPLOYING:
ws2089 [11:29am] [home/efikayd/bin] -> ./restart
Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details.
ws2089 [11:29am] [home/efikayd/bin] ->
SERVER LOG:
[#|2008-01-03T11:29:00.542+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]
[#|2008-01-03T11:29:09.482+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar;|ADM1006:Uploading the file to:[/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar]|#]
[#|2008-01-03T11:29:12.399+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Thread-32;|deployed with moduleid = InboundReceiverMDBModule|#]
[#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;InboundMessageReceiverMDB;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|MDB00017: [InboundMessageReceiverMDB]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
[#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|com.sun.enterprise.connectors.ConnectorRuntimeException
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
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:597)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
|#]
[#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
[#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|appId=InboundReceiverMDBModule moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_InboundReceiverMDBModule ejbName=InboundMessageReceiverMDB|#]
[#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|LDR5004: UnExpected error occured while creating ejb container
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
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:597)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
|#]
[#|2008-01-03T11:29:12.745+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|CORE5020: Error while loading ejb module|#]
[#|2008-01-03T11:29:12.747+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|ADM1075:Error on listening event:[Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ]|#] -
Terracotta: application deploy problem (WLP 9.2)
hi,
when i try to deploy a Portal application on a bea weblogic server (9.2.1), that is enabled for terracotta (added the java startup arguments to the bea server and the client is visible in the Terracotta Administrator Console), the deployment fails and a lot of compile errors are shown concerning bea classes (from netuix.jar and content.jar, see bottom for snippet). for some reason bea wants to compile these classes on deployment.
has anybody seen this same problem and does anybody have a solution or workaround for this problem? must the classes be compiled on the fly during development?
regards,
erik
log snippet:
####<Oct 4, 2007 6:48:49 PM CEST> <Error> <Deployer> <opteron-w2k3> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1191516529616> <BEA-149205> <Failed to initialize the application 'ps' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
Unable to deploy EJB: netuix.jar from netuix.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\wsrp\services\persistence\internal\ProducerPersistenceManager_7vyoe8_Impl.java:11: com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Intf
public final class ProducerPersistenceManager_7vyoe8_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\BookDefinitionManager_1xzrxc_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Intf
public final class BookDefinitionManager_1xzrxc_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortletCategoryManager_uhkdka_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Intf
public final class PortletCategoryManager_uhkdka_Impl
[MORE CLASSES HERE]
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortalDefinitionManager_d875a8_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Intf
public final class PortalDefinitionManager_d875a8_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PageDefinitionManager_c4el9c_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Intf
public final class PageDefinitionManager_c4el9c_Impl
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
25 errors
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)the deployment problem is solved by putting the bea packages in the exclude section of the Terracotta configuration file.
-
Deployment problem to the managed server in 11.1.1.1..
Our deployment problem still continue. We can deploy at last one application to the admin server.
We can see ADF domain ans jsf libs in deployment list
But for managed server following error occurs.
Even we tried small new application.
But error is the same.
An error occurred during activation of changes, please see the log for details.
weblogic.management.DeploymentException:
oracle.mds.lcm.weblogic.WLLifecycleListener
Failure occurred in the execution of deployment request with ID '1247067738026' for task '16'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: oracle.jsp.next, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 for Application Application1_application1
Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.1.0 for Application Application1_application1last error we take is (we are not even use MDS customisation)
Failure occurred in the execution of deployment request with ID '1247124709107' for task '2'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) -
BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)
Hello anybody,
learnt XA being necessary if more than one sql command in transaction, so I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now I receive the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
start() failed on resource 'OracleDB' Unexpected error during start for XAResource
'OracleDB': null
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.deploy(Application.java:247)
at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
KlausHi Klaus,
if you want to implement a global transaction over two different JDBC Resource Managers
(update on both + 2PC) they have to be both XA compliant.
Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
and configuring a TXDataSource with "enable two-phase commit" = true (but only one
non-XA JDBC driver at a time can participate in a distributed transaction).
Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
transactions or distributed transactions without XA drivers as well (using a single
resource manager).
But if you want to update multiple resource managers in the same transaction using
EJBs, this is a "global" transaction, and WL server fully supports it.
But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
Sergi
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
>
Hi Sergi, hello world,
thanks a lot for this message. So the conclusion is that I hava no chance
at all
to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
a prerequisite
for EJB are XA-transactions.
Is this conclusion correct.
Many thanks again
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
distributed transaction (XA) features require version
Oracle8i release 8.1.6 or later of the Oracle server.
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hi Sergi,
1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
2.) I didn´t use a special driver but that that was delivered with thewls
server
in the package "weblogic.jar".
Could I enable you helping me with this information?
Best wishes
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
which
1) Oracle server version (I don't think it's a 8.3.2.)
2) Oracle JDBC driver version
are you you using ?
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hello anybody,
learnt XA being necessary if more than one sql command in transaction,so
I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now
I
receive
the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating itsSQL
Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction
branch
start() failed on resource 'OracleDB' Unexpected error during start
for
XAResource
'OracleDB': null
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.deploy(Application.java:247)
at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus -
Ejb and jsproc deployment problems
Am trying to deploy the java stored procedure (jsp) example
(jsproc subdirectory in acmevideo directory) and the enterprise
java bean (ejb) example (ejb subdirectory in acmevideo
directory). Both use the business and util subdirectries of
acmevideo directory. These examples are provided with
JDeveloper.
In the case of the jsp example, the files compile fine in
JDeveloper. The deployment profile file is created okay using
the Stored Procedure Profile Wizard. But when the jsp is
attempted to be deployed by right clicking the deployment
profile file menu in JDeveloper, the following errors appear:
SQL error during creation of acmevideo/util/DataWrapper
ORA-00922 - missing or invalid option
SQL error during creation of acmevideo/business/TitleQueries
ORA-00922 - missing or invalid option
Is there a corrective action for these errors? Are the details
recorded in any log so that these errors can be troubleshooted?
In the case of the jbe example, the files compile fine in
JDeveloper. The deployment profile file is created okay using
the EJB Profile Wizard. But when the jsp is attempted to be
deployed by right clicking the deployment profile file menu in
JDeveloper, the following happens:
The message indicating that the deployment will take a few
minues continues to show forever. There is no completion,
and one is forced to cancel the process.
This happens when using the port settings of 1521, 1526 (Oracle
listener ports) or 2651 (OAS ORB port). Specifying the service
or omitting it yeilds the same results.
Is there a corrective action for this? Are the details recorded
in any log so that these errors can be troubleshooted?
For both the situations, is the classpath variable need to set
outside the JDeveloper environment?
Also am not able to locate the Oracle 8i CORBA and Enterprise
Java Beans Developer's Guide and the Oracle 8i Java Stored
Procedure Developer's Guide referenced in Building Java
Applications for Oracle 8i anywhere.
Would appreciate any help in this area.
null: Has anyone been able to deploy an ejb from JDeveloper2 (Beta)?
We have ;) But I guess that doesn't count... Please have a look
at the online demo for Enterprise JavaBeans on this technet
website. You can get there through the JDeveloper Tech Info page.
Please open a new thread if that doesn't help you.
Thanks,
-Roel.
phil gulesian (guest) wrote:
: mark tomlinson (guest) wrote:
: : pretty sure the first one is a bug that is fixed in a later
: : build of JDeveloper (JSP deployment problem).
: : As for the EJB deployment problem, here is the way to catch
: what
: : is really going on (in the Beta build -- this will be done
much
: : better in the production build):
: : -edit the jdeveloper.ini (in the BIN directory), in the
: : [environment] section add:
: : LogConsole=1
: : -edit the jdeveloper.properties file (in the LIB directory)
: : change the line :
: : jdeveloper.logOutput=nul
: : to
: : jdeveloper.logOutput=-
: : Now when you run JDeveloper, you will get an output onsole
: : window for the JVM running JDeveloper. You will be able to
see
: : the deployment messages for the EJB wizard being sent to this
: : console. This will allow you to troubleshoot what is
happening.
: I had the same experience as Bansi (above) when I tried to
deploy
: a simple ejb. Following your suggestions about looking in the
: output console window for the JVM, I observed the message
: "PropertyEditor for borland.sql.dataset.ProcedureDescriptor
could
: not be registered ........" A subsequent search found no
: ProcedureDescriptor in the borland.sql.dataset package.
: Has anyone been able to deploy an ejb from JDeveloper2 (Beta)?
null -
Hi,
I have an application developed in JSC2_1 and migrated to VWP/NetBeans which I can run nicely on Sun Java Application Server 9.1. But I am trying to deploy it on tomcat server (5.5.17.,5.5.20) over few weeks. I even assembled tomcat server 6.0.14 and added jstl.jar, jsf-api.jar, jsf-impl.jar and tools.jar (from sun java jdk1.6.0_01) to the common library. Initially I got errors which I rectified. Now if I browse with mozilla firefox I see two panels and images and buttons are not loaded. If I use IE7 I find nothing. Log files do not show any error at all...Can anyone help with these deployment problems with tomcat??
thanks in advance.
dr. am mohan raoI have deployed my JSC 2.1 app to Tomcat 5.5.17 servers.
My app is running on XP Pro (development server) and WIndows 2000 Server (deployment).
I'm using MySQL as the database server.
Did you export your WAR file as J2EE 1.4?
Here are some links that might help:
http://forum.java.sun.com/thread.jspa?threadID=5101183
http://blogs.sun.com/david/entry/defining_java_studio_creator_2
http://blogs.sun.com/winston/entry/redploying_to_tomcat -
CRIO deployment problem error: -1967357951
Hi,
When I connect to my cRIO-9073 an error message show up that it could not find all the libaries.
When I Ignore this and continue i am unable to load my VI's on the host PC and the real-time target.
I think I have installed all the necessary software on the cRIO.
A description of the problem can be found in the attached PDF.
The labview program can be found in attachement.
Best regards,
Jasper
Solved!
Go to Solution.
Attachments:
cRIO deployment problem.pdf 329 KB
cRIO deployment problem.pdf 329 KB
Open loop BLDC control V11_02V2.zip 652 KBHello Jasper,
I have seen this issue before in combination with a (availible) memory problem on the controller. I can see you have quite a lot installed on the cRIO controller. The cRIO-9073 is around already for a couple of years and is limited in terms of avaiable memory comparing to our newer controllers. I saw you are using LabVIEW 2013 which has a bigger footprint then the LabVIEW versions that where around when the cRIO-9073 saw the daylight. I would advise to format the controller and only install the bare minimum which your application needs to the controller and try again. That way we can check whether this issue arrizes from a memory issue or something else.
Regards,
Rik Prins, CLD
Applications Engineering Specialist Northern Europe, National Instruments
Please tip your answer providers with kudos.
Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense -
HELP: JSP deployment problems
Hi,
We have been working hard to resolve our deployment problems, but we are stuck at the following point.
We create the following directory tree.
htdocs/debis/
htdocs/debis/WEB-INF/
htdocs/debis/welcome.jsp
htdocs/debis/mail/
htdocs/denis/mail/readmail.jsp
welcome.jsp works fine.
now the problem is readmail.jsp cannot access the beans in the WEB-INF. mail tries to become a new application root. So we added another WEB-INF under mail, but then it turned out that different application roots are unable to share sessions. What we want to achieve is to have one application root, with several sub applications which are sharing sessions.
Currently we put all jsp files in the
htdocs/debis
directory to make it work. However the directory is now full of jsp files, which we are having hard time determining which belongs to which sub application.
What should we do?
null<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by RamkumarP:
Where is the Bean class? Is it directly under WEB-INF or under the WEB-INF/classes folder? Have you created a classes folder under WEB-INF?<HR></BLOCKQUOTE>
Hi, I am a newbie in running JSP in Apache with Oracle 9iAS. I have only worked with JSPs in Tomcat. Please bear with me.
Before I can run the JSPs in the htdocs/myJSPapp/, beans & servlets in htdocs/myJSPapp/WEB-INF/ folder, what do I need to have installed ?
Is it OSE + mod_ose + Apache + 9iAS ?
Or is there a better alternative for serving out JSPs ?
Thanks! -
ODI Lightweight Designer Installation Problem on AIX
Hi guys,
I have installed oracledilwd on OAS 10.1.3.1.0 and encountered a problem while accessing the same.
The installation for ODI 10.1.3.5 has been done on IBM AIX 5.2 and the deployement of oracledilwd.war on the OAS instance.
the master and work repositories have been crated as weel as the data sources.
I have got the metadata navigator working but although the Lightweight designer got successfully deployed the .war file for the same yet when i test the lwd application i am returned "HTTP 500 - Internal server error" and on checking the ascontrol.log file
This is what i get..
*WARN jmx.JMXUserManager _store.319 - Exception received during persist user info.*
com.phaos.ASN1.ASN1FormatException: java.lang.ArrayIndexOutOfBoundsException
at com.phaos.cert.PKCS12Safe.input(PKCS12Safe)
at com.phaos.cert.PKCS12Safe.<init>(PKCS12Safe)
at com.phaos.cert.PKCS12.input(PKCS12)
at com.phaos.cert.PKCS12.<init>(PKCS12)
at oracle.security.pki.OracleKeyStoreSpi.b(OracleKeyStoreSpi)
at oracle.security.pki.OracleSecretStore.setStoreInWallet(OracleSecretStore)
at oracle.security.pki.OracleWallet.setSecretStore(OracleWallet)
at oracle.sysman.ias.studio.jmx.SecureWalletManager.setEntry(SecureWalletManager.java:129)
at oracle.sysman.ias.studio.jmx.JMXUserManager._store(JMXUserManager.java:307)
at oracle.sysman.ias.studio.jmx.JMXUserManager.setCredential(JMXUserManager.java:250)
Can you guys give any insight regards to the same, am not having any clue.
Cheers
Dhrubo
Edited by: Dhrubo C on Aug 28, 2009 8:02 PMHi Dhrubo,
May be this is an issue with the JVM(IBM).Check Once.
Thanks,
katukota -
EJB2 application on Weblogic10 appc and deployment problem
Hi,
I am trying to migrate my EJB2.0 application from WLS7 jdk4 to WLS10 jdk5. I compiled my application with jdk5 and WLS10 libraries then I am trying to run weblogic.appc on my application it complains that there is some class missing (see the below exception) .. then i try to deploy the jar without running appc on it.. i am getting another exception.. Please help if i am missing any library that is used by appc. I tried to look into all the jars shipped with WLS10 but unable to find that class..
weblogic.appc exception
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/descriptor/BeanUpdateListen
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at weblogic.logging.MessageLogger.<clinit>(MessageLogger.java:45)
at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:51)
at weblogic.j2ee.J2EELogger.logAppcFailedWithError(J2EELogger.java:5257)
at weblogic.application.compiler.Appc.runBody(Appc.java:174)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.Appc.main(Appc.java:183)
at weblogic.appc.main(appc.java:14)
Deployment exception on WLS10
<Aug 24, 2007 9:58:09 AM PKT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor /ecds/bea100/user_projects/domains/
fmsdomain/servers/AdminServer/upload/FMS-raw.jar/META-INF/ejb-jar.xml of module FMS-raw.jar. The error is weblogic.descr
iptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoade
r2.java:774)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java
:395)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoa
der2.java:745)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:7
54)
at weblogic.ejb.spi.EjbJarDescriptor.getEjbJarBean(EjbJarDescriptor.java:131)
at weblogic.ejb.spi.EjbJarDescriptor.getEditableEjbJarBean(EjbJarDescriptor.java:171)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processEjbJarXMLWithSchema(EjbDescriptorReaderImpl.java
:673)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processEjbJarXML(EjbDescriptorReaderImpl.java:220)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createDescriptorFromJarFile(EjbDescriptorReaderImpl.jav
a:172)
at weblogic.ejb.spi.EjbDescriptorFactory.createDescriptorFromJarFile(EjbDescriptorFactory.java:73)
at weblogic.application.compiler.EJBModule.merge(EJBModule.java:130)
at weblogic.application.compiler.flow.SingleModuleMergeFlow.proecessModule(SingleModuleMergeFlow.java:16)
at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:31)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.ReadOnlyEjbMerger.merge(ReadOnlyEjbMerger.java:27)
at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:94)
at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:47)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:137)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.AppMerge.merge(AppMerge.java:149)
at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:70)
at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:51)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeploya
bleObjectFactoryImpl.java:177)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createLazyDeployableObject(WebLogicDep
loyableObjectFactoryImpl.java:150)Sorry for delayed reply. Actually my problem related to deployment is resolved. There were duplicate entries of the same name in the ejb-jar.xml and it seems that weblogic10 parser is more strict on that. I have successfully build and deployed my application on WL10 at AIX. But i am still having problem to run appc on windows. Its throwing the following exception
[java] Created working directory: C:\DOCUME~1\kymsh2\LOCALS~1\Temp\appcgen_1188625950850_FMS-raw.jar
[java] [GC 8128K->3358K(130112K), 0.0161498 secs]
[java] [GC 11486K->5074K(130112K), 0.0172815 secs]
[java] [GC 13202K->5831K(130112K), 0.0129304 secs]
[java] [GC 13959K->6728K(130112K), 0.0116495 secs]
[java] <Sep 1, 2007 10:52:38 AM GMT+05:00> <Error> <J2EE> <BEA-160197> <Unable to load descriptor E:\FMSAntBuild\WL
S10_Build\jars\FMS-raw.jar/META-INF/ejb-jar.xml of module FMS-raw.jar. The error is java.io.IOException
[java] at weblogic.descriptor.internal.MarshallerFactory.<init>(MarshallerFactory.java:50)
[java] at weblogic.descriptor.BasicDescriptorManager.getMarshallerFactory(BasicDescriptorManager.java:131)
[java] at weblogic.descriptor.BasicDescriptorManager.getDescriptorFactory(BasicDescriptorManager.java:165)
[java] at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:289)
[java] at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescrip
torLoader2.java:774)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoad
er2.java:395)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescr
iptorLoader2.java:745)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader
2.java:754)
[java] at weblogic.ejb.spi.EjbJarDescriptor.getEjbJarBean(EjbJarDescriptor.java:131)
[java] at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processEjbJarXMLWithSchema(EjbDescriptorReaderI
mpl.java:671)
[java] at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processEjbJarXML(EjbDescriptorReaderImpl.java:2
20)
[java] at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescript
orReaderImpl.java:185)
[java] at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:9
3)
[java] at weblogic.ejb.container.ejbc.EJBCompiler.parseDescriptors(EJBCompiler.java:1430)
[java] at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:467)
[java] at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:298)
[java] at weblogic.application.compiler.EJBModule.compile(EJBModule.java:83)
[java] at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.jav
a:16)
[java] at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:31)
[java] at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
[java] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
[java] at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
[java] at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
[java] at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:25)
[java] at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:118)
[java] at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:43)
[java] at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
[java] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
[java] at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
[java] at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
[java] at weblogic.application.compiler.Appc.runBody(Appc.java:172)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[java] at weblogic.application.compiler.Appc.main(Appc.java:183)
[java] at weblogic.appc.main(appc.java:14)
[java] Caused by: com.bea.xml.XmlException: unable to load type library from classloader sun.misc.Launcher$AppClass
Loader@133056f
[java] at com.bea.staxb.runtime.internal.BindingContextFactoryImpl.createBindingContext(BindingContextFactoryIm
pl.java:50)
[java] at weblogic.descriptor.internal.MarshallerFactory.<init>(MarshallerFactory.java:48)
[java] ... 35 more
[java] .>
[java] com.bea.xml.XmlException: unable to load type library from classloader sun.misc.Launcher$AppClassLoader@1330
56f
[java] at com.bea.staxb.runtime.internal.BindingContextFactoryImpl.createBindingContext(BindingContextFactoryIm
pl.java:50)
[java] at weblogic.descriptor.internal.MarshallerFactory.<init>(MarshallerFactory.java:48)
[java] at weblogic.descriptor.BasicDescriptorManager.getMarshallerFactory(BasicDescriptorManager.java:131)
[java] at weblogic.descriptor.BasicDescriptorManager.getDescriptorFactory(BasicDescriptorManager.java:165)
[java] at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:289)
[java] at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescrip
torLoader2.java:774)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoad
er2.java:395)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescr
iptorLoader2.java:745)
[java] at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader
2.java:754)
[java] at weblogic.ejb.spi.EjbJarDescriptor.getEjbJarBean(EjbJarDescriptor.java:131)
[java] at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processEjbJarXMLWithSchema(EjbDescriptorReaderI
mpl.java:671)
[java] at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processEjbJarXML(EjbDescriptorReaderImpl.java:2
20)
[java] at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescript
orReaderImpl.java:185)
[java] at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:9
3)
[java] at weblogic.ejb.container.ejbc.EJBCompiler.parseDescriptors(EJBCompiler.java:1430)
[java] at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:467)
[java] at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:298)
[java] at weblogic.application.compiler.EJBModule.compile(EJBModule.java:83)
[java] at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.jav
a:16)
[java] at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:31)
[java] at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
[java] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
[java] at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
[java] at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
[java] at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:25)
[java] at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:118)
[java] at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:43)
[java] at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
[java] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
[java] at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
[java] at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
[java] at weblogic.application.compiler.Appc.runBody(Appc.java:172)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[java] at weblogic.application.compiler.Appc.main(Appc.java:183)
[java] at weblogic.appc.main(appc.java:14)
[java] unable to load type library from classloader sun.misc.Launcher$AppClassLoader@133056f
[java] Java Result: 1
**** ANY IDEA.. ANY BODY ??? ************* -
Deployment problem - invalid username/password
I've developed application using UIX/Struts/ADF BC4J technology. This application was developed on JDeveloper 9.0.5.2 in Windows. When I deployed this application to Application Server (9.0.4) on platform AIX it throws exception "Invalid username/password". When I copied entire project to JDeveloper (9.0.5.2) on AIX and deployed from there everything was OK.
So where is problem when I deployed it from Windows?
Thanks, Martin.Hi!
I looks that you pass the wrong username/password when deploying or that you haven't set up your adminuser and password on the server (set up with your initial "java -jar orions.jar -install" command).
Make sure there is a non-deactivated adminuser in your $J2EE_HOME/config/principals.xml on the OC4J server.
<user username="admin" password="admin">
<description>The default administrator</description>
<group-membership group="administrators" />
<group-membership group="guests" />
<group-membership group="users" />
</user>
Dunno if this is your problem...
Regards
/Stefan Fdgersten, InfoGrator
Maybe you are looking for
-
Unable to insert record in table
Hi, I want to insert record in database table, but when I execute insert command(at When List changed trigger) as select from query and issue commit, the form trying to insert record from datablock which is obviously having empty items, how can I com
-
I used the demo program BCALV_GRID_EDIT to implement my editable grid and now I got stuck in the method data_changed, where I do that loop: LOOP AT rr_data_changed->mt_good_cells INTO ls_mod_cells. where I check, get the values and modify the cells.
-
Hello, I am relatively new to Apple Products and I have a Mac Book Pro and I recently upgraded it from OX X 10.8.6 and I am now running OS X 10.9.1. I had been using Boot Camp and running Windows 7. No issues. When the Mavericks update was complete
-
Exporting images in bridge CS5
for some reason when we go to export images we have adjusted in Bridge CS5, the only option that comes up is "hard drive".. when we select that we have no idea where it is exporting to. On our desktop we have other options like Facebook, and any plac
-
"corrupted" iPod -how can I save my music
It seems that my 15 month old iPod (sod's law its just out of warantee) is corrupted. It will play the first 20s of some tunes, all of others and some not at all. I've just battled to get my computer to see it it for about an hour and finally i get t