Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] problems with deployment to IBM portal server

I'm not sure ;) However, the "linkage error" suggests to me that the JoinPointStaticPart is expecting one or more classes to have a different structure than they do in the test environment. However, I don't know the internals of these things well enough to be certain. Someone from the AJ team may have better insight.

I assume you are using load-time weaving (LTW), since you appear to be advising JSPs. In this case, AspectJ is using a class loader to weave in the advice as the class files are loaded. This is implied by the error message. 

I just googled "websphere jdk" and it looks like WAS 5 uses JDK 1.4 while WAS 6 adds support for JDK 1.5. Could you be using different JDK's or at least different VMs (even if you're using the same version compiler)?  LTW works differently on 1.4 vs. 1.5. I'm not an expert on the details, but the online documentation for AspectJ should point you in the right direction, if this is really the problem.

Anyway, try Ramnivas' suggestion first!

dean

On Mar 21, 2007, at 9:11 AM, Marian Harbach wrote:


Are you sure that this issue is specially important if I use aspects? Because building *.war files locally without aop-support (on WAS 5 with Portal 5.1 as i mentioned before) and deploying them to the test env (WAS 6 and Portal 5.1) is no problem at all and works just fine for a longer period of time. Furthermore a colleague just told me that there were some problems setting up the local environment to match the test, that could not be resolved easily...

Thanks for your reply anyway!

Marian

aspectj-users-bounces@xxxxxxxxxxx schrieb am 21.03.2007 15:01:16:

> Uh, actually, it might be whatever "wrapper" code WAS uses to
> support servlets, but basically it's the same issue....

>
> On Mar 21, 2007, at 8:59 AM, Dean Wampler wrote:

>
> You should confirm this, but I think the versions of the Servlet API
> bundled with WAS 5 and 6 are different. You'll need to build with
> compatible versions. Can you set up your local system to match the
> test environment?

>
> dean

>
> On Mar 21, 2007, at 5:48 AM, Marian Harbach wrote:

>
>
> Hi folkz,
>
> I am currently testing some AOP-stuff using aspectj and AJDT on my
> RAD v6 for our IBM Portal Server environment here. After testing
> locally, I wanted to deploy a small sample portlet with a very
> simple aspect to central test environment. Though it worked well on
> my local WAS/Portal server, the deployment failed remotely showing
> the following error after restarting the app:
>
> [3/21/07 9:55:46:342 CET] 000006d0 WebApp        E   SRVE0026E:
> [Servlet Error]-[LDAPGroupInfoPortlet]: java.lang.Exception:        
>                                                                    
>                                                     java.lang.
> LinkageError: Class org/aspectj/lang/JoinPoint$StaticPart violates
> loader constraints:  definition mismatch betwe                      
>                                                                    
>                                      en parent and child loaders
>         at com.ibm.ws.webcontainer.servlet.ServletWrapper.
> loadServlet(ServletWrapper.java(Compiled Code))
>         at com.ibm.ws.webcontainer.servlet.ServletWrapper.
> handleRequest(ServletWrapper.java(Compiled Code))
>         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.
> include(WebAppRequestDispatcher.java(Compiled Code))
>         at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletInvokerImpl.
> callMethod(PortletInvokerImpl.java(Compiled Code))
>         at com.ibm.wps.pe.pc.legacy.invoker.impl.PortletInvokerImpl.
> title(PortletInvokerImpl.java(Compiled Code))
>         at com.ibm.wps.pe.pc.legacy.PortletContainerImpl.
> includePortletTitle(PortletContainerImpl.java(Compiled Code))
>         at com.ibm.wps.pe.pc.PortletContainerImpl.
> includePortletTitle(PortletContainerImpl.java(Compiled Code))
>         at com.ibm.wps.engine.tags.PortletTitleTag.
> doStartTag(PortletTitleTag.java(Compiled Code))
>         at com.ibm._jsp._Control.
> _jspx_meth_wps_portletTitle_0(_Control.java(Compiled Code))
>         at com.ibm._jsp._Control._jspService(_Control.java(Compiled Code))
> [...]
>
> We are using WAS v6.0.2 and Portal v5.1.0.3 as test environment, but
> locally I have to use WAS v5.1 with Portal v5.1.
> Does someone have a clue what is going wrong here and if there are
> possibly any major differences related to AOP between the IBM WAS versions?
>
> Thanks for any hints and help in advance!!
>
> Greetings
> Marian Harbach

> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
> Dean Wampler, Ph.D.

> dean at objectmentor.com
> http://www.objectmentor.com
> http://www.aspectprogramming.com
> http://www.contract4j.org
>
> I want my tombstone to say:

>   Unknown Application Error in Dean Wampler.exe.
>   Application Terminated.
>       [Okay]        [Cancel]
>
> Dean Wampler, Ph.D.

> dean at objectmentor.com
> http://www.objectmentor.com
> http://www.aspectprogramming.com
> http://www.contract4j.org
>
> I want my tombstone to say:

>   Unknown Application Error in Dean Wampler.exe.
>   Application Terminated.
>       [Okay]        [Cancel]
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list

Dean Wampler, Ph.D.
dean at objectmentor.com

I want my tombstone to say:
  Unknown Application Error in Dean Wampler.exe.
  Application Terminated.
      [Okay]        [Cancel]




Back to the top