[JBoss JIRA] Created: (JBDS-1099) Verify JBDS update site capacity for Eclipse bits
by Mark Yarborough (JIRA)
Verify JBDS update site capacity for Eclipse bits
-------------------------------------------------
Key: JBDS-1099
URL: https://jira.jboss.org/jira/browse/JBDS-1099
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: Program
Affects Versions: LATER
Reporter: Mark Yarborough
The JBDS team would like to ensure that the JBDS update site has capacity (disk and bandwidth) to support the addition of Eclipse bits. This will ensure that the version of eclipse that users pull is the same version that the JBDS release validated in product QE, and should make updating easier for customers. However, addition of these bits will potentially take more disk space and more download bandwidth, hence this "program" related task jira...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBIDE-8182) "Could not initialize NSS" error entry in log
by Denis Golovin (JIRA)
"Could not initialize NSS" error entry in log
---------------------------------------------
Key: JBIDE-8182
URL: https://issues.jboss.org/browse/JBIDE-8182
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Maxim Areshkau
It doesn't affect Visual Editor, it is still working even right after exception
java.security.ProviderException: Could not initialize NSS
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:201)
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:103)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:262)
at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:244)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:244)
at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:224)
at sun.security.jca.ProviderList.loadAll(ProviderList.java:281)
at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:298)
at sun.security.jca.Providers.getFullProviderList(Providers.java:170)
at java.security.Security.getProviders(Security.java:457)
at org.eclipse.equinox.internal.security.ui.SecurityConfigurationSection.write(SecurityConfigurationSection.java:26)
at org.eclipse.ui.internal.ConfigurationInfo.appendExtensions(ConfigurationInfo.java:107)
at org.eclipse.ui.internal.ConfigurationInfo.getSystemSummary(ConfigurationInfo.java:73)
at org.eclipse.ui.internal.about.AboutSystemPage$1.runInUIThread(AboutSystemPage.java:154)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.dialogs.AboutDialog$1.run(AboutDialog.java:126)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.dialogs.AboutDialog.buttonPressed(AboutDialog.java:121)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.about.AboutHandler.execute(AboutHandler.java:32)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
Caused by: java.io.IOException: /home/eskimo/jbdevstudio-h84-CR1/studio/plugins/org.mozilla.xulrunner.gtk.linux.x86_1.9.1.2/xulrunner/libnssutil3.so: version `NSSUTIL_3.12.5' not found (required by /usr/lib/libnss3.so)
at sun.security.pkcs11.Secmod.nssLoadLibrary(Native Method)
at sun.security.pkcs11.Secmod.initialize(Secmod.java:203)
at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:197)
... 70 more
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBIDE-2791) "duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)" error after creating a newseam project
by Riccardo Serafin (JIRA)
"duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)" error after creating a newseam project
-----------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2791
URL: https://jira.jboss.org/jira/browse/JBIDE-2791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.alpha
Environment: Windows XP, Eclipse 3.4.0, JBoss AS 4.2.3-GA, Seam 2.1.0-BETA1, Java 1.6.0_10-rc
Reporter: Riccardo Serafin
After creating a new Seam project via the wizard (EAR packaging, configuration "Dynamic Web project with Seam 2.0"), starting up JBoss produces the following error:
duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)
Even after removing jboss-seam.jar from the war MANIFEST.INF as suggested here (http://www.seamframework.org/Community/HowToUpdateProjectFrom20To21Seam) the error still occurs.
This is the only other reference that I've found to this error (http://jira.jboss.com/jira/browse/JBSEAM-2981) but it looks slightly unrelated to me.
Stack trace:
19:05:32,116 ERROR [[/hellome]] Excepción enviando evento inicializado de contexto a instancia de escuchador de clase org.jboss.seam.servlet.SeamListener
java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)
at org.jboss.seam.core.Init.checkDuplicateFactoryExpressions(Init.java:222)
at org.jboss.seam.core.Init.checkDuplicateFactory(Init.java:215)
at org.jboss.seam.core.Init.addFactoryValueExpression(Init.java:278)
at org.jboss.seam.init.Initialization.installComponents(Initialization.java:983)
at org.jboss.seam.init.Initialization.init(Initialization.java:631)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
....
I believe also these others warnings might be related to the same problem (which i suspect is duplicate jar in the classpath of the war):
19:49:24,506 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
19:49:25,506 INFO [EARDeployer] Init J2EE application: file:/D:/Java/jboss-4.2.3.GA/server/default/deploy/hellome-ear.ear/
19:49:35,459 WARN [MainDeployer] Found non-jar deployer for jboss-seam.jar: MBeanProxyExt[jboss.ejb3:service=EJB3Deployer]
19:49:42,381 WARN [DeploymentInfo] Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: seam.jboss.org:loader=hellome, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false)
19:50:00,679 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.entity.PersistenceUnitDeployment
19:50:04,976 INFO [TomcatDeployer] deploy, ctxPath=/hellome, warUrl=.../deploy/hellome-ear.ear/hellome.war/
19:50:13,554 WARN [SeamPhaseListener] There should only be one Seam phase listener per application
19:50:20,726 INFO [ServletContextListener] Welcome to Seam 2.1.0.BETA1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBIDE-8032) org.jboss.tools.struts.ui.bot.test :: Skipping tests
by Nick Boldt (JIRA)
org.jboss.tools.struts.ui.bot.test :: Skipping tests
----------------------------------------------------
Key: JBIDE-8032
URL: https://issues.jboss.org/browse/JBIDE-8032
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: struts/shale, testing
Affects Versions: 3.2.0.CR1
Reporter: Nick Boldt
For some reason, this plugin's tests are not run.
http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2...
[INFO] --- maven-osgi-packaging-plugin:0.10.0:package-plugin (default-package-plugin) @ org.jboss.tools.struts.ui.bot.test ---
[INFO] Building jar: /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/target/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT.jar
[INFO]
[INFO] --- tycho-p2-plugin:0.10.0:p2-metadata (default-p2-metadata) @ org.jboss.tools.struts.ui.bot.test ---
[INFO]
[INFO] --- maven-osgi-test-plugin:0.10.0:test (default-test) @ org.jboss.tools.struts.ui.bot.test ---
[INFO] Skipping tests
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ org.jboss.tools.struts.ui.bot.test ---
[INFO] Installing /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/target/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT.jar to /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/m2-repository/org/jboss/tools/struts/tests/org.jboss.tools.struts.ui.bot.test/3.2.0-SNAPSHOT/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT.jar
[INFO] Installing /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/pom.xml to /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/m2-repository/org/jboss/tools/struts/tests/org.jboss.tools.struts.ui.bot.test/3.2.0-SNAPSHOT/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT.pom
[INFO] Installing /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/target/p2content.xml to /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/m2-repository/org/jboss/tools/struts/tests/org.jboss.tools.struts.ui.bot.test/3.2.0-SNAPSHOT/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT-p2metadata.xml
[INFO] Installing /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/target/p2artifacts.xml to /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/m2-repository/org/jboss/tools/struts/tests/org.jboss.tools.struts.ui.bot.test/3.2.0-SNAPSHOT/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT-p2artifacts.xml
[INFO]
[INFO] --- tycho-p2-plugin:0.10.0:update-local-index (default-update-local-index) @ org.jboss.tools.struts.ui.bot.test ---
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBIDE-2735) Error: libapr-1.dll was not found starting JBossAS in JBoss IDE
by hmr_mueller (JIRA)
Error: libapr-1.dll was not found starting JBossAS in JBoss IDE
---------------------------------------------------------------
Key: JBIDE-2735
URL: https://jira.jboss.org/jira/browse/JBIDE-2735
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 2.1.2
Environment: Eclipse: 3.3.1.1
OS: Windows
JBoss AS 4.2.2GA JBossWeb native
Reporter: hmr_mueller
When starting the JBossAS 4.2.2GA with JBoss Web native configured from within a JBoss Server configured with the Eclipse IDE (JBoss Tools), I'm getting the error '... libapr-1.dll was not found ..' as a popup. After closing the popup for 3 times the server starts, but does so with errors when starting the Tomcat https connector. When running the run.bat script from the command line everything works fine.
Tomcat is configured to used the AprLifecycleListener and a https connector for APR (OpenSSL style configuration).
The server launch configuration in eclipse contains the $JBOSS_HOME\bin\native directory in the -Djava.library.path variable
The problem seems to be that the libtcnative-1.dll is loading the libapr-1.dll dynamically but since the Path environment variable does not contain the $JBOSS_HOME\bin\native directory the library is not found (setting this is done by the run.bat script).
If I put the native directory in the Path variable, the server starts up correctly, so just defining the java.library.path in the launch configuration does not suffice.
The problem can be fixed I think, if instead of setting the java.library.path the launch configuration extends the environment (Tab Environment) to contain the native directory in the Path environment variable and changing the class
org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossLaunchConfigType to add this to the 'VMRunnerConfiguration' in the 'actualLaunch' method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month