]]>构徏appfuse2.0.2的时候,会在目根目录下生成一个类似ajcore.20080525.115922.886.txt的文件的问题解决http://www.aygfsteel.com/wiflish/archive/2008/05/25/202705.html想飞的鱼想飞的鱼Sun, 25 May 2008 04:13:00 GMThttp://www.aygfsteel.com/wiflish/archive/2008/05/25/202705.htmlhttp://www.aygfsteel.com/wiflish/comments/202705.htmlhttp://www.aygfsteel.com/wiflish/archive/2008/05/25/202705.html#Feedback0http://www.aygfsteel.com/wiflish/comments/commentRss/202705.htmlhttp://www.aygfsteel.com/wiflish/services/trackbacks/202705.html---- Compiler Messages --- warning bad version number found in D:\repository\.m2\repository\org\aspectj\aspectjrt\1.6.0\aspectjrt-1.6.0.jar expected 1.5.4 found 1.6.0 info directory classpath entry does not exist: C:\Java\jdk1.6.0\jre\lib\sunrsasign.jar info zipfile classpath entry does not exist: C:\Java\jdk1.6.0\jre\classes abort ABORT -- (BCException) Unable to continue, this version of AspectJ supports classes built with weaver version 3.0 but the class org.springframework.beans.factory.aspectj.AbstractBeanConfigurerAspect is version 5.0 when batch building BuildConfig[null] #Files=40
Unable to continue, this version of AspectJ supports classes built with weaver version 3.0 but the class org.springframework.beans.factory.aspectj.AbstractBeanConfigurerAspect is version 5.0 when batch building BuildConfig[null] #Files=40
org.aspectj.weaver.BCException: Unable to continue, this version of AspectJ supports classes built with weaver version 3.0 but the class org.springframework.beans.factory.aspectj.AbstractBeanConfigurerAspect is version 5.0 when batch building BuildConfig[null] #Files=40
at org.aspectj.weaver.bcel.BcelAttributes.readAjAttributes(BcelAttributes.java:53) at org.aspectj.weaver.bcel.BcelObjectType.ensureAspectJAttributesUnpacked(BcelObjectType.java:312) at org.aspectj.weaver.bcel.BcelObjectType.<init>(BcelObjectType.java:142) at org.aspectj.weaver.bcel.BcelWorld.buildBcelDelegate(BcelWorld.java:360) at org.aspectj.weaver.bcel.BcelWorld.addSourceObjectType(BcelWorld.java:422) at org.aspectj.weaver.bcel.BcelWeaver.addAspectsFromJarFile(BcelWeaver.java:250) at org.aspectj.weaver.bcel.BcelWeaver.addLibraryJarFile(BcelWeaver.java:225) at org.aspectj.ajdt.internal.core.builder.AjBuildManager.initBcelWorld(AjBuildManager.java:802) at org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild(AjBuildManager.java:243) at org.aspectj.ajdt.internal.core.builder.AjBuildManager.batchBuild(AjBuildManager.java:180) at org.aspectj.ajdt.ajc.AjdtCommand.doCommand(AjdtCommand.java:112) at org.aspectj.ajdt.ajc.AjdtCommand.runCommand(AjdtCommand.java:60) at org.aspectj.tools.ajc.Main.run(Main.java:378) at org.aspectj.tools.ajc.Main.runMain(Main.java:253) at org.codehaus.mojo.aspectj.AbstractAjcCompiler.execute(AbstractAjcCompiler.java:378) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
]]>weblogicW记http://www.aygfsteel.com/wiflish/archive/2008/03/14/186237.html想飞的鱼想飞的鱼Fri, 14 Mar 2008 03:48:00 GMThttp://www.aygfsteel.com/wiflish/archive/2008/03/14/186237.htmlhttp://www.aygfsteel.com/wiflish/comments/186237.htmlhttp://www.aygfsteel.com/wiflish/archive/2008/03/14/186237.html#Feedback0http://www.aygfsteel.com/wiflish/comments/commentRss/186237.htmlhttp://www.aygfsteel.com/wiflish/services/trackbacks/186237.html 域包含一个称为“管理服务器”的Ҏ WebLogic Server 实例Q它是您配置和管理域中所有资源的中心点,一个域有仅只有一个管理服务器实例?br /> 在生产环境中Q应?Web 应用E序、EJB 和其他资源部|到受管服务器上Q管理服务器只应用于配置和管理目的?br /> 多台受管服务器可以组成一个“群集”,q样可以使用单个理服务器来化对受管服务器实例的理Q现时还可以q负蝲qؓ关键应用E序提供故障转移保护?br /> l织域的基本考虑因素Q?br /> a) 应用E序的逻辑划分。例如,可以用一个域来专门提供最l用户功能(例如购物车)Q而将另一个域专用于后端胦务应用程序?br /> b) 物理位置。可以ؓ企业的不同位|或分支建立单独的域?br /> c) 大小。您可能发现Q将域组l成较小的单元可提高理效率Q可以由不同的系l管理员q行理。相反,您可能发现维护一个域或较数目的域可以ɾl护一致性配|变得更Ҏ?br /> 启动受管服务器的ҎQ?br />1、在weblogic的当前域目录中用命令:startManagedWebLogic [SERVER_NAME] [ADMIN_URL] SERVER_NAME - 待启动的域中的受服务器名字(大小写敏? ADMIN_URL - 理服务器地址包含端口?br /> 如:startManagedWebLogic testManagedServer http://localhost:7001 2、在weblogic的控制台界面启动Q操作: 选择要启动的受管服务器,选择"控制"->"启动停止"->"启动此服?. 此时受管服务器启动失败,会出现类似如下错误信息: 描述: Starting DemoManagedServer server ... 此Q务的说明? 状? FAILED 此Q务的状态? 开始时? Fri Mar 14 11:14:13 CST 2008 启动此Q务的旉? l束旉: Fri Mar 14 11:14:14 CST 2008 完成此Q务的旉? 异常: SecureCommandInvoker: Could not create a socket to the NodeManager running on host 'localhost:5555' to execute command 'online DemoManagedServer', reason: Connection refused: connect. Ensure that the NodeManager on host 'localhost' is configured to listen on port '5555' and that it is actively listening 在执行此d时出现的异常? 日志: dzd的日志?
解决办法Q?br /> Solution 1: To make a managed server start, we need to start the node manager on that machine. You can find the script to start the server in WLS_HOME\server\bin\startNodeManager.cmd or sh.
The order in which we need to start the servers are 1.Start the node manager 2.Start the Admin server 3.Start the specific managed server we need to start.
Solution 2: Have you set up a "Machine" for each of the managed servers ?
You need to do that (extremely simple: Machines --> Config. New (Unix) Machine ), and then under your new machine, configure the listen address under Nodemanager Tab, with the IP of the machine running the ManagedServer.
The problem seems to be with the adress which the N.M. listens: if you telnet localhost 5555, you'll get nothing ("conn refused"), but if you telnet X.X.X.X 5555, you'll get the prompt for the NM ( "Escape character is ]" )
So, if you dont configure the managed server to speak with the nodemanager via real ip address instead of localhost (127.0.0.1), you get nothing.