Issues while migrating form Struts2.3.16 to 2.5.14.1

2018-03-14 Thread Rajvinder Pal 
Hi ,

I have upgraded the mandatory jars. But during websphere startup, i am
getting the below exception:-

[3/14/18 17:44:27:005 IST] 0056 ecs   W
com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl scanJAR unable
to open input stream for resource freemarker/core/_Java8Impl.class in
archive WEB-INF/lib/freemarker-2.3.26-incubating.jar
 java.lang.IllegalArgumentException
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at
com.ibm.ws.ecs.internal.scan.impl.ClassScanner.scanInputStream(ClassScanner.java:147)
at
com.ibm.ws.ecs.internal.scan.impl.ClassScanner.scanInputStream(ClassScanner.java:124)
at
com.ibm.ws.ecs.internal.scan.impl.ClassScanner.scanInputStream(ClassScanner.java:120)
at
com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl.scanJAR(ScannerContextImpl.java:275)
at
com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl.scanJARs(ScannerContextImpl.java:315)
at
com.ibm.ws.ecs.internal.scan.context.impl.WARScannerContext.scanInternal(WARScannerContext.java:76)
at
com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl.scan(ScannerContextImpl.java:87)
at
com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl.getScannedClasses(ScannerContextImpl.java:70)
at
com.ibm.ws.webcontainer.webapp.WebAppImpl.scanForHandlesTypesClasses(WebAppImpl.java:752)
at
com.ibm.ws.webcontainer.webapp.WebAppImpl.initializeServletContainerInitializers(WebAppImpl.java:600)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:409)
at
com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)
at
com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:169)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:749)
at
com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:634)
at
com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:426)
at
com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:718)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1175)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1370)
at
com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:968)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:774)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2182)
at
com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:445)
at
com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at
com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:388)
at
com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:116)
at
com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:994)
at
com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:502)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862

What should i check for the above error?

Re: Issues while migrating form Struts2.3.16 to 2.5.14.1

2018-03-14 Thread Adam Brin 
I'd look at the different versions of ASM you have installed both directly
and indirectly in our pom as a first guess.

On Wed, Mar 14, 2018 at 5:30 AM, Rajvinder Pal 
wrote:

> Hi ,
>
> I have upgraded the mandatory jars. But during websphere startup, i am
> getting the below exception:-
>
> [3/14/18 17:44:27:005 IST] 0056 ecs   W
> com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl scanJAR
> unable
> to open input stream for resource freemarker/core/_Java8Impl.class in
> archive WEB-INF/lib/freemarker-2.3.26-incubating.jar
>  java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at
> com.ibm.ws.ecs.internal.scan.impl.ClassScanner.
> scanInputStream(ClassScanner.java:147)
> at
> com.ibm.ws.ecs.internal.scan.impl.ClassScanner.
> scanInputStream(ClassScanner.java:124)
> at
> com.ibm.ws.ecs.internal.scan.impl.ClassScanner.
> scanInputStream(ClassScanner.java:120)
> at
> com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl.scanJAR(
> ScannerContextImpl.java:275)
> at
> com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl.scanJARs(
> ScannerContextImpl.java:315)
> at
> com.ibm.ws.ecs.internal.scan.context.impl.WARScannerContext.scanInternal(
> WARScannerContext.java:76)
> at
> com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl.scan(
> ScannerContextImpl.java:87)
> at
> com.ibm.ws.ecs.internal.scan.context.impl.ScannerContextImpl.
> getScannedClasses(ScannerContextImpl.java:70)
> at
> com.ibm.ws.webcontainer.webapp.WebAppImpl.scanForHandlesTypesClasses(
> WebAppImpl.java:752)
> at
> com.ibm.ws.webcontainer.webapp.WebAppImpl.initializeServletContainerInit
> ializers(WebAppImpl.java:600)
> at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(
> WebAppImpl.java:409)
> at
> com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(
> WebGroupImpl.java:88)
> at
> com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(
> VirtualHostImpl.java:169)
> at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(
> WSWebContainer.java:749)
> at
> com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(
> WSWebContainer.java:634)
> at
> com.ibm.ws.webcontainer.component.WebContainerImpl.
> install(WebContainerImpl.java:426)
> at
> com.ibm.ws.webcontainer.component.WebContainerImpl.
> start(WebContainerImpl.java:718)
> at
> com.ibm.ws.runtime.component.ApplicationMgrImpl.start(
> ApplicationMgrImpl.java:1175)
> at
> com.ibm.ws.runtime.component.DeployedApplicationImpl.
> fireDeployedObjectStart(DeployedApplicationImpl.java:1370)
> at
> com.ibm.ws.runtime.component.DeployedModuleImpl.start(
> DeployedModuleImpl.java:639)
> at
> com.ibm.ws.runtime.component.DeployedApplicationImpl.start(
> DeployedApplicationImpl.java:968)
> at
> com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(
> ApplicationMgrImpl.java:774)
> at
> com.ibm.ws.runtime.component.ApplicationMgrImpl.start(
> ApplicationMgrImpl.java:2182)
> at
> com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(
> CompositionUnitMgrImpl.java:445)
> at
> com.ibm.ws.runtime.component.CompositionUnitImpl.start(
> CompositionUnitImpl.java:123)
> at
> com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(
> CompositionUnitMgrImpl.java:388)
> at
> com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$
> 500(CompositionUnitMgrImpl.java:116)
> at
> com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(
> CompositionUnitMgrImpl.java:994)
> at
> com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(
> WsComponentImpl.java:502)
> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862
>
> What should i check for the above error?
>



-- 
_
Adam Brin
Director of Technology, Digital Antiquity
480.965.1278

Re: Struts2 login action class seems to be reused

2018-03-14 Thread Prasanth Pasala 
We had a user report it soon after the deployment. After that we started 
looking into the specific user who reported (User1) and the user (whose 
information was seen by the reporting user) say User2.
We realized there are login entries from same IP for both of these users. In 
the access log of the server there was a POST request for User1 but at the time 
of login entry for User2 there was only a
GET request.  In the time line GET request is first, User1 sees User2's 
information logs out and then login again with their credentials.

Thanks,
Prasanth

On 03/13/2018 11:41 PM, Yasser Zamani wrote:
>
> On 3/10/2018 1:22 AM, Prasanth Pasala wrote:
>> Ran tests with 1000 users logging in in 60sec while simultaneously 1000 
>> users just requesting login page in 60 sec to see if any of them would get 
>> in with out username/password. No luck. System seems
>> to be working properly. Also tried increasing it to 2000 it still worked as 
>> it should with out the issue coming up.
>>
>> Would hot deployments cause any issue?
> Without reproducing it, it's hard to say why this issue happens rarely
> :( How did you discover it firstly? Was incorrectly loged in user able
> to continue to other pages also as an authenticated user?
>
> -
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>

Re: CDI Plugin example does not work in 2.5.14.1

2018-03-14 Thread fullmitten 
Oracle has responded to my service request.  It appears that changes to 
Log4j to support Java 9 break Weblogic's classloader.  There is a new 
bug for this issue: Bug 27098427 : JAVA.LANG.ILLEGALARGUMENTEXCEPTION 
DEPLOYING APP ON WLS 12.1.3 WITH PSU


For now, it is possible to work around this issue by using Log4j 2.8.x.  
I added a dependency for log4j-api and log4j-core, version 2.8.2.  The 
application appears to work fine, thought it does generate a spectacular 
error message covered by this WW-4920, which is apparently addressed in 
Struts 2.5.16.



On 2018-01-22 19:38, fullmit...@lycos.com wrote:


Oracle support has created a bug for this issue:
BUG 27424564 - STRUTS 2.5.14.1 APP BROKEN AT SOME POINT AFTER PSU 
12.1.3.0.160719
I tried downgrading the Weblogic PSU and that appears to work.  One can 
also downgrade the Struts version. Struts 2.5.12 works for me with the 
latest Weblogic PSU. (27057030).


On 2018-01-22 18:11, fullmit...@lycos.com wrote:

I am using Java 1.8.0_131-b11 on Windows 7, 64-bit for both building 
the app and running Weblogic.


I did some more experimenting. I tried removing CDI from my source 
code and the Maven pom.  I still get the error with a complete 
stripped down application (the only dependency being Struts), so CDI 
isn't at issue here.


The word from Oracle is that this problem appears to have been 
introduced into WLS 12.1.3 between the July 2016 and January 2018 
Critical Patch Updates (that is, Struts works with the earlier patch 
and does not work with the latter). I, of course, am running with the 
latest updates.

Thanks.

On 2018-01-21 14:32, Lukasz Lenart wrote:

...

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org