Jsr168 portlet deployment problem in Apache Pluto...

Hi Friends ...i am new to this Apache Pluto..
Accuvally i am trying to deploy my portlets in Apache Pluto 1.1.7 with Tomcat 5.5.20
i tried with the Following procedure
http://portals.apache.org/pluto/v11/deploying.html
but after deploment and when i am hitting the Page i am getting the Problem like
Error rendering portlet.
javax.portlet.PortletException
     at org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:191)
     at org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
     at org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
     at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
     at org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspx_meth_pluto_portlet_0(portlet_002dskin_jsp.java:99)
     at org.apache.jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:74)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
     at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
     at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
     at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
Could any one help in resolving this ...
And i have one more doubt .....
Using Maven tool and creating WAR ... is this compulsory to Deploy any portlet in Apache Pluto ?+
Thanks & Regards
Suresh.Vadlamudi

Similar Messages

Oracle 9i Lite Mobile Server deploye Problem As Apache Module

I am trying to get the Oracle9i Lite Mobile Server run as a Module under Apache.
my platform is Linux 7.2, which of course is documented as an option.
I managed to install the mobile server and the following document is
the latest from ORACLE site. and is very useful.
http://technet.oracle.com/docs/products/lite/doc_library/release501/readme.htm#new
I have one problem to overcome the module to load in Apache
'libwtgapach.so'
is the required shared library.
This does not load due to following error,
Cannot load /var/ORACLE/mobile/server/bin/libwtgapach.so into server:
/var/ORACLE/mobile/server/bin/libwtgapach.so: undefined symbol:
ap_global_ctx
All the libraries can be resolved here is the ldd ( link map )
ldd libwtgapach.so
liborafc.so => /var/ORACLE/mobile/server/bin/liborafc.so (0x40007000)
libjvm.so => /var/ORACLE/jdk/jre/lib/i386/classic/libjvm.so
(0x4002a000) libhpi.so =>
/var/ORACLE/jdk/jre/lib/i386/green_threads/libhpi.so (0x400bd000)
libdl.so.2 => /lib/libdl.so.2 (0x400dd000)
libpthread.so.0 => /lib/i686/libpthread.so.0 (0x400e1000)
libstdc++-libc6.1-1.so.2 => /usr/lib/libstdc++-libc6.1-1.so.2
(0x400f7000)
libm.so.6 => /lib/i686/libm.so.6 (0x40139000)
libc.so.6 => /lib/i686/libc.so.6 (0x4015c000)
libnsl.so.1 => /lib/libnsl.so.1 (0x40297000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
I found this post explaining to recompile Apache
This actually means you installed mod_ssl as a DSO, but
. without rebuilding Apache with EAPI. Because EAPI is a
requirement for mod_ssl, you need an extra patched Apache
(containing the EAPI patches) and you have to build this
Apache with EAPI enabled (explicitly specify --enable-rule=EAPI
at the APACI command line).I recompiled apache with the following
./configure --prefix=/usr/local/ssl-apache/httpd-2.0.39
--enable-rule=EAPI ; make ; make install
I still get the same error when I try to load the module.Am I missing
something?
Any help is deeply appreciated.
-- ajith

Scott, I have yet to get WTG server to work as an NT service when loaded as an Apache module.
We've had to load it into a non-service based Apache server (one that runs from the command line in a MS-DOS prompt window). This is on XP Pro.
We've switched to running our WTG server on Linux.

Writing a JSR168 portlet WITHOUT using Jdeveloper or "wizards"

I have a JSR168 portlet that is built using Maven (http://maven.apache.org/ if you don't know what that is).
It deploys and operates perfectly well into a portlet container such as Pluto (the standard, reference container from Apache).
Pluto supplies a Maven plugin, that takes the vanilla web.xml and other configuration e.g. portlet.xml and adds the necessary configuration to run the portlet in the container. I believe there is an Ant plugin that does exactly the same thing.
It adds the following conf to teh web.xml;
<servlet>
<servlet-name>my-portlet-name</servlet-name>
<servlet-class>org.apache.pluto.core.PortletServlet</servlet-class>
<init-param>
<param-name>portlet-name</param-name>
<param-value>my-portlet-name</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>my-portlet-name</servlet-name>
<url-pattern>/PlutoInvoker/my-portlet-name</url-pattern>
</servlet-mapping>
This is the "magic" that glues my portlet to the portlet container.
What I wish to know, is how to make my JSR168 portlet deploy into Oracle Portal 10g without EVER using JDeveloper. What is the 'magic' I have to apply to my web.xml or portlet.xml or other configuration that will men I can deploy my portlet war into the app server and make it talk turkey with the portal container. I can cope with just having a customised web.xml that I have to copy into the WAR file if need be ... if I could find some guidance what should be in that file.
It seems that every search I've done in google or though the doco we have here starts with "Start Jdeveloper and select XXX in the portlet wizard".
I do not use Jdeveloper and nor will I. I will continue to build my Java code in a correct fashion, i.e. on the command line with my standard build tools that don't involve the IDE. Don't get me wrong, I use an IDE, but one should never be mandated. In my book, "wizards" are about the worst imaginable way to get any programming task completed.

Hi Marcel
With respect, it's patently obvious that we know how to develop a portlet without Jdeveloper, because if you read the message you would have been able to discern that this is the way we are accustomed to doing it, and it's faster, easier and more portable that way. I've been doing J2EE development since the first version of the spec and well before there was an Oracle implementation of it.
You don't actually need an EAR file, as a WAR will suffice and the dcmctl command-line utility can supply everything else in its arguments (like, context-path and the like), and it allows each WAR artifact to be deployed in different times, i.e. when they are built on the integration server. I find EAR files usually too heavyweight especially as I rarely write EJBs, as opposed to using e.g. Spring.
Using the web browser is not an option for automated deployment and acceptance testing from an integration build server.
Configuring the portal side of things looks decidedly a different matter and I've not found anyway to do it from the command line, it demands the browser, which is a let-down.
It's terribly disappointing the paucity of information about automation of deployment as opposed to the positively verdant amount of presentations, tutorials and documentation that assumes top-to-bottom Oracle tooling and environment and browser-based configuration. Even where it's actually possible Oracle doesn't seem to want to tell people about it or do as I believe they should, which is regard this form of deployment and configuration as the default way to teach developers how to use their products. None of this helps build and deploy to Oracle products using test-driven development, continuous integration, and automated acceptance testing, all of which are usually regarded as essential parts of a modern developers toolkit by the best minds in the business.
So after we're left alone to discover how to do this by ourselves for a month you can forgive my disappointment at being lectured like I was some neophyte who doesn't know how to make a WAR file with textedit.

Problem deploying JSR168 portlets; Tomcat, Win2003

Dear All,
Am having some problems deploying the JSR168 portlets on Tomcat 4.1 and Win2003.
This is on Windows, and I have to manually deploy it per the instructions...
So far I__
1. Exploded the .war and added ptjsr168 to pthome.xml per the sparse installation pdf;
2. stopped tomcat, deleted the cache (contents of the work directory), restarted.
3. verified that the application appears in the work directory
but get the error,
/PtPortletContainer/portlet/RssPortlet/mode/view
descriptionThe requested resource (/PtPortletContainer/) is not available.
...when I try to browse there to get the correct URL tp paste into the remote server, something like:
http://portlets.mycustomer.com:8080/ptjsr168/
The extension to this in the web service is, by default:
/PtPortletContainer/portlet/RssPortlet/mode/view
I may be typing the URL wrong, for all I know. Something simple.
Any ideas?
Cheers,
Rob

You can verify whether your portlet works correctly by testing it on OpenPortal Portlet Container(https://portlet-container.dev.java.net). Or if you think the issue is with Pluto Portal I would recommend posting your issue on the Pluto Portal mail alias.

Deploy jsr168 portlet in weblogic

Hi,
I'm developing a jsr168 portlet that I would like to be able to deploy in the Weblogic Portal (among others).
The problem is, after much searching, that I can't figure out how to do it.
In Websphere I just deploy the .war file through the portal administration web interface and away I go.
In jetspeed2 I just drop the .war file in the deploy folder and it gets deployed.
Is there anything similar for Weblogic?
I've currently got 8.1 SP4 installed.
I've seen and even tried the portletPreparer tool but I can't get it to work (dependencies on bea classes that I can't find).
Any help or tips on how to deploy a portlet in a .war file would be greatly appreciated.
Cheers,
Eric

Hi,
Generally while creating a jar file for deplyong a EJB on an App Server, create a folder called META-INF and copy all your xml files to this folder
this command could be part of your build.xml if ur using ant
mkdir build build\META-INF
copy *.xml build\META-INF
Then compile ur java files and then create the required jar or ear file for deployment.
Rgds,
Seetesh

Problem:programmatically portlet deployment

Hi ...
I want to programmatically deploy a portlet application in a portal's HOME page.
For this i have identified following four steps:
1. First step is to copy the J2EE resources of the portlet in a specific directory.
2. Change the portal configuration file named xyz.portal to add this new
portlet in the portal's HOME page.
3. Run the "SYNC" utility to refresh the portal server.
4. Now set the portlet properties "Visible" and "Available" to true.
I am able to do things till step 3.
Now i have two questions?
1. I am able to set the property "visible" to true (by modifying the portletname.portlet
file - mandatory element) but i could not find a way to directly
set the "available property" to true. How can i do this programmatically.
2. Is there a better way of doing the above four steps (for eg is there some utility
which does the portlet deployment)
Regards,
Ubhay.

Resolved it! :)
This was the consequence of deploying portlets with invalid descriptor (not sure which one - web.xml or portal.xml - i will investigate later).
It seems that Portal Server tries to reload all these portlets during
"deploy redeploy" task.
I use my own classes on portal, so executing "deploy redeploy" task is crucial for me. CLI171 error blocks the execution of this task!
So, i deleted invalid wars and their descriptors from
/var/opt/SUNWps/tmp/portlet/ and restarted application server - this
solves the problem completely - and now i able to use "deploy redeploy".
This tip may be useful during active portlet deployment:) Beware of CLI171 error! :)
Vad.

Edit mode in JSR168 Portlet

Hi all,
I m using Portal version 10.1.4 and developing JSR168 Portlet using JDeveloper 10.1.2.1.0 (Build 1913).
There is a edit mode in my portlet and i have done entry for this mode in portlet.xml and also implemented doEdit() method.
inside doEdit() method i have also written response.setContentType("text/html");
Successfully deployed the .ear and also registered the WSDL url.
But when i click on the Personalize link of the portlet then a page comes with a message
Error: Could not get markup. The cookie or session is invalid or there is a runtime exception.
And the error in wsrp_default_island_1\application.txt is
javax.portlet.PortletModeException: Portlet mode "edit" is not allowed in current context
at oracle.webdb.wsrp.server.PortletURLImpl.setPortletMode(Unknown Source)
Could any one tell me where i m doing wrong.
help will be appreciated..
Thnx
~Neeraj Sidhaye
Try_Catch_Finally @ Y !
ExtremePortal @ Gmail Dot Com

Hi Harsha,
Actually there is a problem with setPortletMode method of PortletURL.
When i use
PortletURL portletURL=renderResponse.createActionURL();
portletURL.setPortletMode(PortletMode.EDIT); (Although it is not required , but in case if situation occurs like if i want to change the mode then it will fail)
In this case if i click on Personalize link then it is throwing an exception.
Is it bug with Oracle Portal , i don't know....
When i comment that code then every thing is working perfectly for me
and the required jsp is rendering in Edit mode of the Portlet.
Comments ans Suggestions are welcome at 24*7 :-)
Thnx
~Neeraj Sidhaye
Try_Cactch_Finally @ Y !
ExtremePortal @ Gmail Dot Com

JSR168 portlet packaging?

From the JSR168 spec, (which is similar to how other portals seem to behave
with their proprietary APIs), a JSR168 portlet application appears to be a
WAR with a portlet.xml and web.xml conforming to the requirements of the
spec, that can then be installed in any portal.
From my superficial knowledge based on skimming the WL8.1 portal docs
recently, WL portlet development appears to be done within a Portal WAR such
that the portlet(s) are just components of the portal war itself.
How are these two supposed to work together in the WLP env? Say I develop a
couple JSR168 portlets in my own Java environment (emacs :-) and then WAR
them up and install them into Jetspeed-2 and another 168 compliant portal
when available (eg, IBM's 5.something). I believe those would accept my
portlet WAR and keep them in that WAR and just reference them from their
Portals. How would WL8.1.x handle such development (outside of Workshop/WL)
and deployment to a WL8.1.x portal? Do I have to merge my JSR168 based
portlet WAR (and thus a web.xml and portlet.xml merge) into the Portal WAR
(eg, if I want to ship a script to deploy my portlet WAR into an existing
WL8.1 portal?) or will WL8.1.x be able to reference a Portlet WAR outside of
a Portal WAR?
TIA - a confused potential portlet developer...

I agree with what Joe said...
BTW, I (and I assume Joe) think JSR168 is a good thing - and it's great that
WLP has the first prototype of it out there - don't get me wrong, I like it,
I'd just prefer if it were easier to deploy to given portlets coming in from
multiple sources being added into an existing portal. From Joe's case, he
probably doesn't want to have to merge the portlet.xml files. From my case
as a supplier of portlets, I'd rather not have to have to create different
install tools/docs/procedures for my customers for each portal vendor now
that I can have standard portlets based on JSR168...
"Joe C." <[email protected]> wrote in message
news:[email protected]...
You can always import any arbitrary webapp using the WLW as a portalproject
I'm not sure that solves my problem or the one ISV was talking about(which
I assume is the same).
I am not talking about importing a webapp (containing portlets or nto) and
making it be my portal.
- Assume I'm already developing a portal with some in-house developed
portlets.
- I want to get 3 JSR168 portlets from SAP (just picked a random vendorout
of the air) and add them to my portal.
- I want to get 2 JSR168 portlets from Siebel (ditto)
- And I need one Domino portlet from that other 3 letter vendor (ditto)
- Each of those vendors is likely to build JSR168 portlets that can be
installed/used in any JSR168 compliant portal, so they can stop buildingall
the various per-vendor proprietary API portlets.
- Each of those vendors needs to package up their portlets for
shipping/install.
- Given that JSR168 describes the Web App layout for packaging a portlet,
each of those vendors is likely to package their portlets up in a WAR.
- Some JSR168 compliant portals (I believe) will be able to just install
those WARs and use them as is from the Portal WAR and drop them on pages.
- WLP 8.1 appears to require that I unpack/extract those WARs and mergethe
portlet.xml and contents of each of those WARs with my existing Portal WAR
that I want to add those portlets to. Tell me why this is better?
To your earlier comments made here:
The pitfall of this approach is that webapps depend on each other towork correctly
Well yeah, I expect my portal to depend on my portlets - of course.
which is against the spirit of webapps.I disagree - EARs depend on the WARs within them. Cooperating WARs can
depend on each other too.
A deployer should be able to deploy/undeploy any webapp withoutaffecting the functionality of other
webapps - which would be case in the model you describe.Of course, if you remove a portlet that a portal depends on, I wouldexpect
it to break .
In addition, there are security issues that the deployer must be awareof.
Of course. That's the case with any J2EE deployment no matter how many
EARs/WARs you're deployiing.
"Subbu Allamaraju" <[email protected]> wrote in message
news:[email protected]...
Joe,
You can always import any arbitrary webapp using the WLW as a portal
project, and during that process you'll have the opportunity to
automatically update the descriptors (and also adding the correct jar
files). There is no need to hand-merge descriptors unless you want to.
Subbu
Joe C. wrote:
Please tell me it's going to get better.
That would make sense if one were developing all their own portlets
for
their portals.
But I (and most people I know) as a customer, that needs to aggregate
portlets from multiple (possibly many) 3rd parties, such as the big 4
application vendors, am going to need to know how those standardJSR168
portlets work and are configured so that I can hand-merge them into my
company's portal?
As an end user it doesn't really help me that much that I can developmy
own
portlets to JSR168. The whole point of JSR168 is that portlet vendorsthat
build portlets for others to install into their portals will be able
to
build one set of portlets that can then be installed in any compliant
portal. This limitation seems to prevent that from beingcommonplace/useful
(given how few people are going to know how to do such merges - theyjust
want to install 3rd party portlets and drop them on pages). I reallyhope
Workshop provides a user friendly way to integrate such 3rd party
JSR168
portlets or WLP will be missing the whole point of having such astandard in
the first place. I agree with the ISV that started this
conversation -
please provide a means for me to install 3rd party portlets withouthaving
to hand-merge XML configuration files.
"Subbu Allamaraju" <[email protected]> wrote in message
news:[email protected]...
isv wrote:
From the JSR168 spec, (which is similar to how other portals seem to
behave
with their proprietary APIs), a JSR168 portlet application appears to
be
a
WAR with a portlet.xml and web.xml conforming to the requirements of
the
spec, that can then be installed in any portal.For all practical purposes, a portal app is a web app, with the only
differece being the portlet.xml file. So, a portal app contains
portlets
in addition to things that typically exist in a webapp.
How are these two supposed to work together in the WLP env? Say I
develop a
couple JSR168 portlets in my own Java environment (emacs :-) and thenWAR
them up and install them into Jetspeed-2 and another 168 compliantportal
when available (eg, IBM's 5.something). I believe those would accept
my
portlet WAR and keep them in that WAR and just reference them fromtheir
Portals. How would WL8.1.x handle such development (outside ofWorkshop/WL)
and deployment to a WL8.1.x portal? Do I have to merge my JSR168
based
portlet WAR (and thus a web.xml and portlet.xml merge) into thePortal
>>>
WAR
(eg, if I want to ship a script to deploy my portlet WAR into anexisting
WL8.1 portal?) or will WL8.1.x be able to reference a Portlet WARoutside of
a Portal WAR?For WLP, the unit of development/deployment is a webapp. We're aware
that some implementations (including the ones you mention) follow a
model where portal deployment involves several web apps with portlets
aggregated by a portal deployed in one of those webapps. The pitfall
of
this approach is that webapps depend on each other to work correctly -
which is against the spirit of webapps. A deployer should be able to
deploy/undeploy any webapp without affecting the functionality ofother
webapps - which would be case in the model you describe. In addition,
there are security issues that the deployer must be aware of.
Having said this, if your portlets are already bundled into a WARfile,
you need to merge the portlets into the portal webapp. Or, you couldlet
WL convert your webapp into a portal webapp. We don't intend tosupport
portlet referencing from other webapps.
Subbu

JSR168 Portlet Exception with Oracle OC4J and Spring

JSR168 Portlet Exception with Oracle OC4J and Spring
I’m having a problem with accessing a Spring JSR168 Portlet when deployed on Oracle OC4J. I have created a very simple portlet that just renders simple jsp page. I created two versions. One using GenricPortlet and one using org.springframework.web.portlet.mvc.AbstractContro ller. The non-Spring portlet deploys and runs as expected. The Spring portlet deploys but throws the following exception
Code:
07/11/05 08:23:44 [ERROR] DispatcherPortlet - Could not complete request <javax.portlet.PortletException>javax.portlet.PortletExcept
ion
at oracle.portlet.server.containerimpl.RequestDispatcherImpl.include(RequestDispatcherImpl.java:74)
at org.springframework.web.portlet.DispatcherPortlet.render(DispatcherPortlet.java:1077)
at org.springframework.web.portlet.DispatcherPortlet.doRenderService(DispatcherPortlet.java:809)
at org.springframework.web.portlet.FrameworkPortlet.processRequest(FrameworkPortlet.java:475)
at org.springframework.web.portlet.FrameworkPortlet.doDispatch(FrameworkPortlet.java:445)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:163)
at oracle.portlet.server.containerimpl.ServerImpl.getMarkup(ServerImpl.java:161)
at oracle.portlet.wsrp.v1.WSRPv1ToServer.getMarkup(WSRPv1ToServer.java:4512)
at oracle.portlet.wsrp.v1.WSRP_v1_Markup_PortTypeSoapToJaxb.getMarkup(WSRP_v1_Markup_PortTypeSoapToJaxb.java:68)
at oasis.names.tc.wsrp.v1.bind.runtime.WSRP_v1_Markup_Binding_SOAP_Tie.invoke_getMarkup(WSRP_v1_Markup_Binding_SOAP_Tie.java
:60)
at oasis.names.tc.wsrp.v1.bind.runtime.WSRP_v1_Markup_Binding_SOAP_Tie.processingHook(WSRP_v1_Markup_Binding_SOAP_Tie.java:7
79)
at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:297)
at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:413)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:277)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:134)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.portlet.server.service.ContextFilter.doFilter(ContextFilter.java:86)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
Caused by: javax.servlet.ServletException: Error in servlet
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:759)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_include(ServletRequestDispatcher.java:160)
at com.evermind.server.http.ServletRequestDispatcher.access$000(ServletRequestDispatcher.java:51)
at com.evermind.server.http.ServletRequestDispatcher$1.oc4jRun(ServletRequestDispatcher.java:97)
at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:102)
at oracle.portlet.server.containerimpl.RequestDispatcherImpl.include(RequestDispatcherImpl.java:65)
... 34 more
Nested Exception is javax.servlet.ServletException: Error in servlet
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:759)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_include(ServletRequestDispatcher.java:160)
at com.evermind.server.http.ServletRequestDispatcher.access$000(ServletRequestDispatcher.java:51)
at com.evermind.server.http.ServletRequestDispatcher$1.oc4jRun(ServletRequestDispatcher.java:97)
at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:102)
at oracle.portlet.server.containerimpl.RequestDispatcherImpl.include(RequestDispatcherImpl.java:65)
at org.springframework.web.portlet.DispatcherPortlet.render(DispatcherPortlet.java:1077)
at org.springframework.web.portlet.DispatcherPortlet.doRenderService(DispatcherPortlet.java:809)
at org.springframework.web.portlet.FrameworkPortlet.processRequest(FrameworkPortlet.java:475)
at org.springframework.web.portlet.FrameworkPortlet.doDispatch(FrameworkPortlet.java:445)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:163)
at oracle.portlet.server.containerimpl.ServerImpl.getMarkup(ServerImpl.java:161)
at oracle.portlet.wsrp.v1.WSRPv1ToServer.getMarkup(WSRPv1ToServer.java:4512)
at oracle.portlet.wsrp.v1.WSRP_v1_Markup_PortTypeSoapToJaxb.getMarkup(WSRP_v1_Markup_PortTypeSoapToJaxb.java:68)
at oasis.names.tc.wsrp.v1.bind.runtime.WSRP_v1_Markup_Binding_SOAP_Tie.invoke_getMarkup(WSRP_v1_Markup_Binding_SOAP_Tie.java
:60)
at oasis.names.tc.wsrp.v1.bind.runtime.WSRP_v1_Markup_Binding_SOAP_Tie.processingHook(WSRP_v1_Markup_Binding_SOAP_Tie.java:7
79)
at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:297)
at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:413)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:277)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:134)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.portlet.server.service.ContextFilter.doFilter(ContextFilter.java:86)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
2007-11-05 08:23:44.085 WARNING An internal error has occurred in method getMarkup()
I have managed to deploy and run the Spring portlet using Sun App Server and Sun Portlet container with no problems which leads me to believe my Spring setup is correct.
I also have managed to run the Spring pets portlet example on Sun App Server and Sun Portlet container with no problems. But again it fails on Oracle with the same problem.
To deploy on Oracle I ran the oracle wsrp jar against my EAR. As far as I can tell it has not corrupted any of the Spring setup in the web.xml.
The version are as follows
Oracle Portal 10.1.4 running on OAS 10.1.2
calling the portlet using WSRP v1.
The portlet is running on standalone OC4J 10.1.3.3 with Oracle portlet container 10.1.3.2. On Windows Spring 2.0.6.
Any ideas? Thanks Paul

Was an answer ever found? I am currently experiencing the same issue.
Edited by: user10567841 on Nov 8, 2008 12:21 PM

Jsr168 portlet issue

Hi,
1. I developped two jsr168 portlet and deployed them to java portlet container successfully, but the status of one is always not loaded, against, the status of the other is loaded, do you why?
2. i want to add the portlet which its status is loaded to my page, but I cann't find it in the portal builder. Do you know where is it or how to find it or how to add a jsr168 portlet to a page after deploying it?
thanks very much
jason

Thanks very much for your reply.
because i don't want to use the JDeveloper to help me to develop and deploy the jsr168 compliant portlet on oracleAS10g Portal, so my question is that how to add my jsr168 portlet to a page when i deploy it successfully?
In fact, I already finish developping the jsr168 portlet and deploy it to java portlet container on oralceAS10g successfully. but i cann't find it in the portal builder, so i don't know how to add it to my page. can you give me more information about it in detail? I don't think i can get enough information from the developer's guild pdf document, i read it, but i still cann't figure out my problem.
thanks again
jason

Right problem with apache and tomcat

Bonjour;
I use a user login "apache" to stop/start Apache and tomcat. Because never launching apache et tomcat as root.
But I have the following problem with apache (file error.log) :
[Tue May 6 17:26:22 2003] [error] Connection "warpConnection" cannot connect
[Tue May 6 17:26:22 2003] [error] Cannot open connection "warpConnection"
[Tue May 6 17:27:01 2003] [error] Re-Trying to deploy connections
As root the error msg does'nt exists (lost)
Best regards;
A+;

Run it from the shell to see whats wrong:
# httpd

Getting error while working with jsr168 portlet in weblogic portal 10.1

Hi,
I have configured jsr168 portlet to display RSS feed.I am not getting any error when I have logged in for 2 to 3 times. It's displaying fine.After that when I again login I am getting this error.
I am not knowing what's the problem is?Let me know.
java.lang.NullPointerException at com.bea.portlet.container.UserInfo.getAllProperties(UserInfo.java:149) at com.bea.portlet.container.UserInfo.updateUserInfo(UserInfo.java:117) at com.bea.portlet.container.AppContainer.invokeRender(AppContainer.java:704) at com.bea.netuix.servlets.controls.content.JavaPortletContent.fireRender(JavaPortletContent.java:249) at com.bea.netuix.servlets.controls.content.JavaPortletContent.renderInternal(JavaPortletContent.java:156) at com.bea.netuix.servlets.controls.content.JavaPortletContent.beginRender(JavaPortletContent.java:103) at com.bea.netuix.servlets.controls.application.laf.ContentControlRenderer.beginRender(ContentControlRenderer.java:48) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326) at com.bea.netuix.nf.UIControl.render(UIControl.java:582) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._pcagreen.__flowlayout._jspService(__flowlayout.java:290) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326) at com.bea.netuix.nf.UIControl.render(UIControl.java:582) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._pcagreen.__gridlayout._jspService(__gridlayout.java:292) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388) at com.bea.netuix.servlets.manager.UIServlet.processControlTree(UIServlet.java:301) at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:927) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.documentum.web.servlet.CompressionFilter.doFilter(CompressionFilter.java:108) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.documentum.web.env.WDKController.processRequest(WDKController.java:95) at com.documentum.web.env.WDKController.doFilter(WDKController.java:83) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.documentum.web.env.PortalRequestFilter.doFilter(PortalRequestFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200) at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Edited by jhansi.mandalapu at 05/05/2008 11:20 PM
Edited by jhansi.mandalapu at 05/05/2008 11:30 PM

Thanks Brad !!!
It works...
earlier I had entitlements set only on Employee Portal and Calendar in the tree structure Community_repository > Calendar > EmployeePortal > Calendar.
It didnt work and throwed that error.
After your suggestion I set entitlements on groupware.calendar.appointment to create, view, update, delete and instantiate to true.
It worked, thanks for your help.
-Win

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. ]|#]

How to debug JSR168 portlets

Hi,
Is there a way to debug the jsr168 portlets from Jdeveloper, possibly using remote debugging feature? If yes, appreciate step-by-step instruction on this.
I have posted a query related to remote debugging here:
Remote Debugging (Jdev 10.1.3 to AS 10.1.3)
Thanks,
Pandian.

I'm not sure I understand your question. It sounds like you have JSF (faces) components and JSP pages; do you also have JSR168 portlets? The WEB-INF/portlet.xml file should have nothing to do with JSF / JSP pages; it is used only to declare JSR168 portlets.
To try and answer your question though, if you have JSR168 portlets listed in WEB-INF/portlet.xml, these portlets should show up in the administrative tools when the webapp deploys.

How to expose JSR168 portlets from existing JSF webapp?

Hi all,
I have a web application with JSF components, and a set of JSP pages that use these components. In WEB-INF, I also have a standard portlet.xml which describes what JSP page to expose for the declared portlet(s).
Is there any administrative interface in the WebLogic Portal that would automatically detect these portlets as soon as I deploy the webapp, so that I can display them ? My idea is that as soon as this webapp with the portlet.xml is deployed, my portlets should be added to the list of available portlets somewhere. Is that so with the WebLogic portal ? Thanks very much for your feedback.
P.S: I am using WebLogic Portal 10.0
Regards,
Angel

I'm not sure I understand your question. It sounds like you have JSF (faces) components and JSP pages; do you also have JSR168 portlets? The WEB-INF/portlet.xml file should have nothing to do with JSF / JSP pages; it is used only to declare JSR168 portlets.
To try and answer your question though, if you have JSR168 portlets listed in WEB-INF/portlet.xml, these portlets should show up in the administrative tools when the webapp deploys.

Jsr168 portlet deployment problem in Apache Pluto...

Similar Messages

Maybe you are looking for