Re: [aspectj-users] Server slowdown

2014-10-14 Thread Anthony Mayfield
Thanks Ryan, I found out it was because some code deeper down was creating a
parser each time.  I think you might be right as the parser created a
hashmap each time.  It's very frustrating this takes over 100 times longer
on the server though, the specs are quite similar between my server and
laptop.  I'll just have to eliminate the parser from the code somehow. 

 

 http://www.aplossystems.co.uk/ aplosLogoSmall

A : Aplos Systems Ltd, 17 Carlton Place, Southampton, SO15 2DY.

T : 0800 520 0690

 

Registered in England, 111 rattle Road, Westham, Pevensey, East Sussex, BN24
5DH; Registration number 6657177

 

From: aspectj-users-boun...@eclipse.org
[mailto:aspectj-users-boun...@eclipse.org] On Behalf Of Ryan Gardner
Sent: 14 October 2014 02:22
To: aspectj-users@eclipse.org
Subject: Re: [aspectj-users] Server slowdown

 

Are those maps concurrent maps? If not, map resizing of a standard hashmap
when being accessed via multi threads can cause CPU spikes like that.

On Oct 13, 2014 5:22 PM, Anthony Mayfield i...@aplossystems.co.uk wrote:

Hi,

 

It's ok, it looks like the issue lies with the code inside the aspect that
is getting called.  I'm still not sure why it would take so long on the
server and not on my laptop but it doesn't look related to the aspect coding
directly,

 

All the best,

 

Anthony.

 

 http://www.aplossystems.co.uk/ aplosLogoSmall

A : Aplos Systems Ltd, 17 Carlton Place, Southampton, SO15 2DY.

T : 0800 520 0690

 

Registered in England, 111 rattle Road, Westham, Pevensey, East Sussex, BN24
5DH; Registration number 6657177

 


___
aspectj-users mailing list
aspectj-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users

___
aspectj-users mailing list
aspectj-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: [aspectj-users] Aspectj in weaving a jar file

2014-10-14 Thread mufc_fan
I have one more doubt... I am adding aspects to hadoop source code and I
imported one of the package and created aspect aj file but while running I
have to choose main function but it seems no class of this package have main
function...What I have to do?...Plz help me...



--
View this message in context: 
http://aspectj.2085585.n4.nabble.com/Aspectj-in-weaving-a-jar-file-tp4651584p4651605.html
Sent from the AspectJ - users mailing list archive at Nabble.com.
___
aspectj-users mailing list
aspectj-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users


Re: [aspectj-users] Aspectj in weaving a jar file

2014-10-14 Thread mufc_fan
can you share a link or any other on how to create a configuration
manually...also is it mandatory to mention the main class in the
configuration?



--
View this message in context: 
http://aspectj.2085585.n4.nabble.com/Aspectj-in-weaving-a-jar-file-tp4651584p4651607.html
Sent from the AspectJ - users mailing list archive at Nabble.com.
___
aspectj-users mailing list
aspectj-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users


[aspectj-users] Stackmap frame errors when building the aspectj project with Java 1.7

2014-10-14 Thread Heshan Suriyaarachchi
Hi,

I have a project which is using aspectj and it is building fine with Java
1.6. When I update it to Java 1.7 I'm seeing following error.

[INFO] Molva the Destroyer Aspects ... FAILURE [2.324s]
[INFO] Molva The Destroyer Client  SKIPPED
[INFO] Molva The Destroyer Parent  SKIPPED
[INFO] Molva The Destroyer Distribution .. SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 2.424s
[INFO] Finished at: Tue Oct 14 11:16:19 PDT 2014
[INFO] Final Memory: 12M/310M
[INFO]

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1:java
(default) on project molva-the-destroyer-aspects: An exception occured
while executing the Java class. Expecting a stackmap frame at branch target
30
[ERROR] Exception Details:
[ERROR] Location:
[ERROR] com/concur/puma/molva/aspects/TestTarget.main([Ljava/lang/String;)V
@12: invokestatic
[ERROR] Reason:
[ERROR] Expected stackmap frame at this location.
[ERROR] Bytecode:
[ERROR] 000: 2a4d b200 5e01 012c b800 644e b800 c62d
[ERROR] 010: b600 ca2c 2db8 00bb 2db8 00bf 57b1 3a04
[ERROR] 020: b800 c62d 1904 b600 ce19 04bf
[ERROR] Exception Handler Table:
[ERROR] bci [12, 30] = handler: 30
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException



This is what my maven configuration looks like.
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
dependency
groupIdorg.aspectj/groupId
artifactIdaspectjrt/artifactId
version1.6.5/version
/dependency
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version1.2.17/version
/dependency
dependency
groupIdorg.perf4j/groupId
artifactIdperf4j/artifactId
version0.9.16/version
/dependency
/dependencies

build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdaspectj-maven-plugin/artifactId
version1.2/version
configuration
source1.7/source
target1.7/target
/configuration
executions
execution
goals
goalcompile/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.1/version
executions
execution
phasepackage/phase
goals
goaljava/goal
/goals
/execution
/executions
configuration

mainClasscom.concur.puma.molva.aspects.TestTarget/mainClass
/configuration
/plugin
/plugins
/build

The TestTarget class is a simple class (Pasting it here for completeness.)
public class TestTarget {

static Logger logger = Logger.getLogger(TestTarget.class);

public static void main(String[] args) throws Exception {
// Test case 01
new TestTarget().test1();

// Test case 02
for(int i=0;i10;i++) {
testCountFast(1000);
}

// Test case 03
for(int i=0;i5;i++) {
testCountSlow(1000);
}

// Test case 04
//new TestTarget().test2();
}

public static void testCountSlow(int value) {
count(value,5);
System.out.println(slow count executed!);
//logger.info(Slow count complete!);
}

public static void testCountFast(int value) {
count(value,0);
System.out.println(fast count executed!);
//logger.info(Fast count complete!);
}

private static void count(int value, int delay) {
for (int i=0;ivalue;i++) {
try {
Thread.sleep(delay);
} catch (Exception e) {
logger.error(Error occurred while sleeping the thread
count, e);
}
}
}

public void test1() {
//logger.info(TestTarget.test());
}

public void 

Re: [aspectj-users] Stackmap frame errors when building the aspectj project with Java 1.7

2014-10-14 Thread Frank Pavageau
2014-10-14 21:28 GMT+02:00 Andy Clement andrew.clem...@gmail.com:

 I’d recommend updating to a more recent AspectJ.  Older AspectJs did have
 issues with making mistakes generating stack map frames.  The option to use
 split verifier was only possible with JDK1.6 I think, with 1.7 they removed
 that capability so the stack map frames needed to be correct.


For the record, -XX:-UseSplitVerifier is available in the Hotspot JVM 7 to
disable the new verifier which needs correct stack map frames. It's not
available in the Hotspot JVM 8 anymore.

Frank
___
aspectj-users mailing list
aspectj-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: [aspectj-users] Stackmap frame errors when building the aspectj project with Java 1.7

2014-10-14 Thread Alexander Kriegisch
Yes, the default compliance level is 1.4 according to 
http://mojo.codehaus.org/aspectj-maven-plugin/compile-mojo.html#complianceLevel,
 even in the current plugin version 1.7 (you still use 1.5, I recommend an 
update there as well, not just in the AspectJ runtime).
-- 
Alexander Kriegisch
http://scrum-master.de


 Am 14.10.2014 um 23:08 schrieb Heshan Suriyaarachchi 
 heshan.suriyaarach...@gmail.com:
 
 Thank you for the quick feedback guys. 
 
 I tried updating to the latest aspectj jars too. Still I saw the same error. 
 Then I found out the error. I was missing the complianceLevel tag in my 
 plugin configuration. 
 
 Pasting the updated aspectj-maven-plugin configuration in case someone runs 
 into the same issue that I ran into. 
 
  plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdaspectj-maven-plugin/artifactId
 version1.5/version
 configuration
 complianceLevel1.7/complianceLevel
 source1.7/source
 target1.7/target
 /configuration
 executions
 execution
 !--phaseprocess-sources/phase--
 goals
 goalcompile/goal
 goaltest-compile/goal
 /goals
 /execution
 /executions
 /plugin
 
 Thanks, 
 Heshan.
 
 On Tue, Oct 14, 2014 at 1:43 PM, Frank Pavageau frank.pavag...@gmail.com 
 wrote:
 2014-10-14 21:28 GMT+02:00 Andy Clement andrew.clem...@gmail.com:
 
 I’d recommend updating to a more recent AspectJ.  Older AspectJs did have 
 issues with making mistakes generating stack map frames.  The option to use 
 split verifier was only possible with JDK1.6 I think, with 1.7 they removed 
 that capability so the stack map frames needed to be correct.
 
 For the record, -XX:-UseSplitVerifier is available in the Hotspot JVM 7 to 
 disable the new verifier which needs correct stack map frames. It's not 
 available in the Hotspot JVM 8 anymore.
 
 Frank
 
 ___
 aspectj-users mailing list
 aspectj-users@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe from 
 this list, visit
 https://dev.eclipse.org/mailman/listinfo/aspectj-users
 
 
 
 -- 
 Regards,
 Heshan Suriyaarachchi
 
 http://heshans.blogspot.com/
 http://www.linkedin.com/in/heshan
 ___
 aspectj-users mailing list
 aspectj-users@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe from 
 this list, visit
 https://dev.eclipse.org/mailman/listinfo/aspectj-users
___
aspectj-users mailing list
aspectj-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: [aspectj-users] Stackmap frame errors when building the aspectj project with Java 1.7

2014-10-14 Thread Alexander Kriegisch
I forgot to mention that AspectJ Maven Plugin 1.7 automatically uses 
aspectjtools 1.8.2 by default, see 
http://mojo.codehaus.org/aspectj-maven-plugin/dependencies.html


 Am 14.10.2014 um 23:19 schrieb Alexander Kriegisch alexan...@kriegisch.name:
 
 Yes, the default compliance level is 1.4 according to 
 http://mojo.codehaus.org/aspectj-maven-plugin/compile-mojo.html#complianceLevel,
  even in the current plugin version 1.7 (you still use 1.5, I recommend an 
 update there as well, not just in the AspectJ runtime).
 -- 
 Alexander Kriegisch
 http://scrum-master.de
 
 
 Am 14.10.2014 um 23:08 schrieb Heshan Suriyaarachchi 
 heshan.suriyaarach...@gmail.com:
 
 Thank you for the quick feedback guys. 
 
 I tried updating to the latest aspectj jars too. Still I saw the same error. 
 Then I found out the error. I was missing the complianceLevel tag in my 
 plugin configuration. 
 
 Pasting the updated aspectj-maven-plugin configuration in case someone runs 
 into the same issue that I ran into. 
 
  plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdaspectj-maven-plugin/artifactId
 version1.5/version
 configuration
 complianceLevel1.7/complianceLevel
 source1.7/source
 target1.7/target
 /configuration
 executions
 execution
 !--phaseprocess-sources/phase--
 goals
 goalcompile/goal
 goaltest-compile/goal
 /goals
 /execution
 /executions
 /plugin
 
 Thanks, 
 Heshan.
 
 On Tue, Oct 14, 2014 at 1:43 PM, Frank Pavageau frank.pavag...@gmail.com 
 wrote:
 2014-10-14 21:28 GMT+02:00 Andy Clement andrew.clem...@gmail.com:
 
 I’d recommend updating to a more recent AspectJ.  Older AspectJs did have 
 issues with making mistakes generating stack map frames.  The option to 
 use split verifier was only possible with JDK1.6 I think, with 1.7 they 
 removed that capability so the stack map frames needed to be correct.
 
 For the record, -XX:-UseSplitVerifier is available in the Hotspot JVM 7 to 
 disable the new verifier which needs correct stack map frames. It's not 
 available in the Hotspot JVM 8 anymore.
 
 Frank
 
 ___
 aspectj-users mailing list
 aspectj-users@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe 
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/aspectj-users
 
 
 
 -- 
 Regards,
 Heshan Suriyaarachchi
 
 http://heshans.blogspot.com/
 http://www.linkedin.com/in/heshan
 ___
 aspectj-users mailing list
 aspectj-users@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe from 
 this list, visit
 https://dev.eclipse.org/mailman/listinfo/aspectj-users
 ___
 aspectj-users mailing list
 aspectj-users@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe from 
 this list, visit
 https://dev.eclipse.org/mailman/listinfo/aspectj-users
___
aspectj-users mailing list
aspectj-users@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users