[JBoss AOP] - Re: Eclipse Error when I use the AOP plugin / Aspect Manager
by xoxol
Hi all :)
I'm using eclipse 3.2.0 (org.jboss.ide.eclipse.jdt.aop.core_1.1.2.GA , org.jboss.ide.eclipse.jdt.aop.ui_1.1.2.GA) and i've this issue too :(
| !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
| !STACK 0
| java.lang.NoSuchMethodError: org.eclipse.jdt.internal.ui.JavaPlugin.getWorkingCopyManager()Lorg/eclipse/jdt/ui/IWorkingCopyManager;
| at org.jboss.ide.eclipse.jdt.aop.ui.editors.AopJavaEditorUtils$AopEditorListener.getCompilationUnit(AopJavaEditorUtils.java:174)
| at org.jboss.ide.eclipse.jdt.aop.ui.editors.AopJavaEditorUtils$AopEditorListener.refreshAdvisedMembers(AopJavaEditorUtils.java:143)
| at org.jboss.ide.eclipse.jdt.aop.ui.editors.AopJavaEditorUtils$AopEditorListener.partActivated(AopJavaEditorUtils.java:138)
| at org.eclipse.ui.internal.PartListenerList2$1.run(PartListenerList2.java:68)
| at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
| at org.eclipse.core.runtime.Platform.run(Platform.java:843)
| at org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:53)
| at org.eclipse.ui.internal.PartListenerList2.firePartActivated(PartListenerList2.java:66)
| at org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:77)
| at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:171)
| at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:56)
| at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:126)
| at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3190)
| at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:588)
| at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2597)
| at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2521)
| at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2513)
| at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2498)
| at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
| at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2493)
| at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2478)
| at org.eclipse.ui.ide.IDE.openEditor(IDE.java:388)
| at org.eclipse.ui.ide.IDE.openEditor(IDE.java:350)
| at org.eclipse.jdt.internal.ui.wizards.NewElementWizard$1.run(NewElementWizard.java:71)
| at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
| at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
| at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325)
| at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
| at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
| at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
| at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
| at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
| at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
| at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
| 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:585)
| at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
| at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
| at org.eclipse.core.launcher.Main.run(Main.java:977)
| at org.eclipse.core.launcher.Main.main(Main.java:952)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013582#4013582
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013582
19Â years, 2Â months
[Messaging, JMS & JBossMQ] - Re: Memory leak caused by Connection$PingTask
by y-komori
I have the same problem on JBoss 3.2.7.
I think the cause is as follows.
1. The "Connection Monitor Thread" which executes the PingTask can't
aquire the semaphore then that thread waits for ever.
2. The "Connection Monitor Thread" is the only thread in the process.
PingTasks created by the other Connections will be held in the memory,
therefore it causes to the memory leak.
3. The Semaphore is locked for ever in the Connection.close().
4. When both PingTask.run() and Connection.close() are executed at the
same time, the problem will sometimes happen.
For reproducing the problem, breaking at "pingTaskSemaphore.acquir()" in
the PingTask.run() using the debugger, then executing Connection.close().
For avoiding the memory leak problem, I think the following treatment
is effective.
1. Change the following line in the PingTask.run().
before : pingTaskSemaphore.acquire()
after : pingTaskSemaphore.attempt(msec)
2. When the "Connection Monitor Thread" failed to aquire the Semaphore,
it skips the PingTask.
I'll be preased if some of JBossMQ's commiter will check that this
problem is JBossMQ's bug and discuss about my treatment?
Thank you.
Yusuke KOMORI / SMG Co.,Ltd.
komori(a)smg.co.jp
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013580#4013580
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013580
19Â years, 2Â months
[JNDI/Naming/Network] - env-entry lookup problem in jboss
by luker74
Hi all,
i'm trying to lookup an env-entry from a java client program, and also from a servlet, but in all cases jboss says that the env-entry is not bound.
I use jboss3.2.8sp1 my code is:
Properties properties = new Properties();
properties.put("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
properties.put("java.naming.factory.url.pkgs",
"org.jboss.naming:org.jnp.interfaces");
properties.put("java.naming.provider.url", "jnp://10.26.1.183:1099");
properties.put("jnp.disableDiscovery", "true");
properties.put("j2ee.clientName", "orologio-client");
InitialContext ic = new InitialContext(properties);
try {
envEntry = (String)ic.lookup("OROLOG");
} catch (NamingException ne) {
throw new ServiceLocatorException(ne);
}
and the ebj-jar.xml is :
<ejb-jar>
<enterprise-beans>
...........
<env-entry>
The caller of the factory
<env-entry-name>OROLOG</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>it.ausystems.progettoejb.dao.OrologioDAOImpl</env-entry-value>
</env-entry>
........
</enterprise-beans>
</ejb-jar>
the problem is:
11:35:47,654 INFO [STDOUT] it.ausystems.progettoejb.dao.OrologioDAOException: javax.naming.NameNotFoundException: OROLOG not bound
can you help me?
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013577#4013577
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013577
19Â years, 2Â months
[Security & JAAS/JBoss] - Re: form based authentication not working under JBoss 4.0.5
by wonker
Bugger, forgot the confgs, sorry:
| *** Login.jsp ***
|
| <FORM method="POST" name="j_security_check" action='<%=response.encodeURL("j_security_check") %>'>
| <input type="text" name="j_username">
| <input type="password" name="j_password">
| <input type="submit" value="Log In">
| </FORM>
|
| *** web.xml ***
|
| <security-constraint>
| <web-resource-collection>
| <web-resource-name>Admin Tool</web-resource-name>
| <description>The Admin site</description>
| <url-pattern>/action/*</url-pattern>
| <http-method>GET</http-method>
| <http-method>POST</http-method>
| <http-method>PUT</http-method>
| </web-resource-collection>
| <auth-constraint>
| <role-name>Admin System</role-name>
| </auth-constraint>
| </security-constraint>
| <login-config>
| <auth-method>FORM</auth-method>
| <realm-name>ADMIN</realm-name>
| <form-login-config>
| <form-login-page>/Login.jsp</form-login-page>
| <form-error-page>/Login.jsp?error=true</form-error-page>
| </form-login-config>
| </login-config>
| <security-role>
| <role-name>Admin System</role-name>
| </security-role>
|
| *** jboss-web.xml ***
|
| <jboss-web>
| <context-root>/admin</context-root>
| <security-domain>java:/jaas/admin-profile</security-domain>
| </jboss-web>
|
| *** login-config.xml ***
|
| <application-policy name="admin-profile">
| <authentication>
| <login-module code="foo.bar.jaas.spi.LdapLoginModule" flag="required">
| <module-option name="noauth">false</module-option>
| <module-option name="debug">false</module-option>
| <module-option name="principalClass">foo.bar.jaas.AdminPrincipal</module-option>
| </login-module>
| </authentication>
| </application-policy>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013572#4013572
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013572
19Â years, 2Â months