[jira] Commented: (GERONIMODEVTOOLS-110) Exception in IModulePublishHelper.getPublishDirectory() for Geronimo
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-110?page=comments#action_12438718 ] Kathy Chan commented on GERONIMODEVTOOLS-110: - Just create a Geronimo targetting Web project with an EAR, create a Java bean in that project, right-click on that bean to bring up Create Web Service wizard, click Finish. You'll see this exception in the console: org.apache.geronimo.kernel.InternalKernelException: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.IOException: Unable to deserialize GBeanData default/g3EAR/1.0/car?configurationName=default/g3EAR/1.0/car at org.apache.geronimo.system.jmx.KernelDelegate.getGBeanData(KernelDelegate.java:762) at org.apache.geronimo.st.v11.core.GeronimoServerBehaviour.getPublishDirectory(GeronimoServerBehaviour.java:179) at org.eclipse.jst.ws.internal.axis.creation.ui.command.CopyDeploymentFileCommand.execute(CopyDeploymentFileCommand.java:99) GeronimoServerBehaviour.getPublishDirectory() is called from CopyDeploymentFileCommand and it returns null. Please let me know if you still have problem reproducing the problem. Exception in IModulePublishHelper.getPublishDirectory() for Geronimo Key: GERONIMODEVTOOLS-110 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-110 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.x Environment: Windows XP Reporter: Kathy Chan Priority: Critical Driver: Geronimo 1.1 unreleased driver g-eclipse-plugin-20060926-2.zip from: http://people.apache.org/dist/geronimo/eclipse/unstable/ On WTP 1.5.1 09/22 0504 driver using Geronimo 1.1.1 Tomcat server. When creating a Web service on g3EAR containing the g3 Web module, we need to call IModulePublishHelper.getPublishDirectory(), here's the resulting exception: org.apache.geronimo.kernel.InternalKernelException: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.IOException: Unable to deserialize GBeanData default/g3EAR/1.0/car?configurationName=default/g3EAR/1.0/car at org.apache.geronimo.system.jmx.KernelDelegate.getGBeanData(KernelDelegate.java:762) at org.apache.geronimo.st.v11.core.GeronimoServerBehaviour.getPublishDirectory(GeronimoServerBehaviour.java:179) at org.eclipse.jst.ws.internal.axis.creation.ui.command.CopyDeploymentFileCommand.execute(CopyDeploymentFileCommand.java:99) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:413) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:353) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:251) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:250) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:851) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:220) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:94) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.performFinish(WizardPageManager.java:250) at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.performFinish(DynamicWizard.java:332) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:680) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:355) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254) at
[jira] Created: (GERONIMODEVTOOLS-110) Exception in IModulePublishHelper.getPublishDirectory() for Geronimo
Exception in IModulePublishHelper.getPublishDirectory() for Geronimo Key: GERONIMODEVTOOLS-110 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-110 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.x Environment: Windows XP Reporter: Kathy Chan Priority: Critical Driver: Geronimo 1.1 unreleased driver g-eclipse-plugin-20060926-2.zip from: http://people.apache.org/dist/geronimo/eclipse/unstable/ On WTP 1.5.1 09/22 0504 driver using Geronimo 1.1.1 Tomcat server. When creating a Web service on g3EAR containing the g3 Web module, we need to call IModulePublishHelper.getPublishDirectory(), here's the resulting exception: org.apache.geronimo.kernel.InternalKernelException: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.IOException: Unable to deserialize GBeanData default/g3EAR/1.0/car?configurationName=default/g3EAR/1.0/car at org.apache.geronimo.system.jmx.KernelDelegate.getGBeanData(KernelDelegate.java:762) at org.apache.geronimo.st.v11.core.GeronimoServerBehaviour.getPublishDirectory(GeronimoServerBehaviour.java:179) at org.eclipse.jst.ws.internal.axis.creation.ui.command.CopyDeploymentFileCommand.execute(CopyDeploymentFileCommand.java:99) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:413) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:353) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:251) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:250) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:851) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:220) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:94) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.performFinish(WizardPageManager.java:250) at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.performFinish(DynamicWizard.java:332) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:680) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:355) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) 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
[jira] Commented: (GERONIMODEVTOOLS-110) Exception in IModulePublishHelper.getPublishDirectory() for Geronimo
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-110?page=comments#action_12438241 ] Kathy Chan commented on GERONIMODEVTOOLS-110: - I also tried with the Geronimo 1.0 server, this time, I was able to have IModulePublishHelper.getPublishDirectory() return properly without an exception for a couple of times but then I got a similar exception later when creating Web services: org.apache.geronimo.kernel.InternalKernelException: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.lang.ClassNotFoundException: org.apache.geronimo.gbean.GBeanData (no security manager: RMI class loader disabled) at org.apache.geronimo.kernel.jmx.KernelDelegate.getGBeanData(KernelDelegate.java:285) at org.apache.geronimo.st.v1.core.GeronimoServerBehaviour.getPublishDirectory(GeronimoServerBehaviour.java:165) at org.eclipse.jst.ws.internal.axis.creation.ui.command.CopyDeploymentFileCommand.execute(CopyDeploymentFileCommand.java:99) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:413) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:353) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:251) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:250) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:851) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:220) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:94) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.performFinish(WizardPageManager.java:250) at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.performFinish(DynamicWizard.java:332) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:680) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:355) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) 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
[jira] Commented: (GERONIMODEVTOOLS-80) Error with create DeploymentUtils.createJarFile() during publish of Geronimo server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-80?page=comments#action_12379157 ] Kathy Chan commented on GERONIMODEVTOOLS-80: Correction: Problem occurs also manuall using server tooling. This problem occurs just by doing the following: - Create and start Geronimo 1.0 server - Create hello.html - Run on server on hello.html Results in the error: !MESSAGE An internal error occurred during: Publishing to Apache Geronimo 1.0 !STACK 0 java.lang.NoSuchMethodError: org.eclipse.wst.common.frameworks.datamodel.IDataModel: method getDefau ltOperation()Lorg/eclipse/wst/common/frameworks/datamodel/IDataModelOperation; not found at org.apache.geronimo.core.DeploymentUtils.createJarFile(DeploymentUtils.java:73) at org.apache.geronimo.core.commands.DistributeCommand.execute(DistributeCommand.java:43) at org.apache.geronimo.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.j ava:77) at org.apache.geronimo.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeployment Op.java:69) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.distribute(GeronimoServerBehavi our.java:337) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviou r.java:258) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBeh aviour.java:230) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBeh aviour.java:214) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDe legate.java:672) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourD elegate.java:752) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate .java:610) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:803) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:791) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) Error with create DeploymentUtils.createJarFile() during publish of Geronimo server --- Key: GERONIMODEVTOOLS-80 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-80 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Versions: 1.0.0 Environment: Windows XP Reporter: Kathy Chan Driver: WTP 1.5 200605091754 + Geronimo 1.0 plugin + Geronimo server When publishing the Geronimo server programmatically using the Web services wizard, I got the error: org.eclipse.wst.common.frameworks.datamodel.IDataModel: method getDefaultOperation()Lorg/eclipse/wst/common/frameworks/datamodel/IDataModelOperation; not found java.lang.NoSuchMethodError: org.eclipse.wst.common.frameworks.datamodel.IDataModel: method getDefaultOperation()Lorg/eclipse/wst/common/frameworks/datamodel/IDataModelOperation; not found at org.apache.geronimo.core.DeploymentUtils.createJarFile(DeploymentUtils.java:73) at org.apache.geronimo.core.commands.DistributeCommand.execute(DistributeCommand.java:43) at org.apache.geronimo.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:77) at org.apache.geronimo.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:69) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.distribute(GeronimoServerBehaviour.java:337) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:258) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:230) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:214) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:672) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:752) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:610) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:803) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:791) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand$1.run(StartServerCommand.java:129) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand.publish(StartServerCommand.java:141) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand.execute(StartServerCommand.java:79) at
[jira] Created: (GERONIMODEVTOOLS-80) Error with create DeploymentUtils.createJarFile() during publish of Geronimo server
Error with create DeploymentUtils.createJarFile() during publish of Geronimo server --- Key: GERONIMODEVTOOLS-80 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-80 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Versions: 1.0.0 Environment: Windows XP Reporter: Kathy Chan Driver: WTP 1.5 200605091754 + Geronimo 1.0 plugin + Geronimo server When publishing the Geronimo server programmatically using the Web services wizard, I got the error: org.eclipse.wst.common.frameworks.datamodel.IDataModel: method getDefaultOperation()Lorg/eclipse/wst/common/frameworks/datamodel/IDataModelOperation; not found java.lang.NoSuchMethodError: org.eclipse.wst.common.frameworks.datamodel.IDataModel: method getDefaultOperation()Lorg/eclipse/wst/common/frameworks/datamodel/IDataModelOperation; not found at org.apache.geronimo.core.DeploymentUtils.createJarFile(DeploymentUtils.java:73) at org.apache.geronimo.core.commands.DistributeCommand.execute(DistributeCommand.java:43) at org.apache.geronimo.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:77) at org.apache.geronimo.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:69) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.distribute(GeronimoServerBehaviour.java:337) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:258) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:230) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:214) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:672) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:752) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:610) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:803) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:791) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand$1.run(StartServerCommand.java:129) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand.publish(StartServerCommand.java:141) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand.execute(StartServerCommand.java:79) at org.eclipse.jst.ws.internal.consumption.ui.server.StartServerWidget$StartServerJob.run(StartServerWidget.java:305) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) I have no problem with starting the server manually using server tooling start server command. I also did not have problem with publishing to Geronimo using Web services wizard using Geronimo 1.0 plugin with the WTP 1.0 driver. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-73) Geronimo needs to support IModulePublishHelper.getPublishDirectory() to get to the server's publish directory
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-73?page=comments#action_12378753
]
Kathy Chan commented on GERONIMODEVTOOLS-73:
As discussed, Geronimo dev tools would implement:
public IPath getPublishDirectory(IModule[] module)
The input IModule[] would either contains one entry, which is the Web module or
two entries, where the first entry is the EAR module and the second entry is
the Web module.
Geronimo needs to support IModulePublishHelper.getPublishDirectory() to get
to the server's publish directory
-
Key: GERONIMODEVTOOLS-73
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-73
Project: Geronimo-Devtools
Type: Bug
Components: eclipse-plugin
Versions: 1.0.0
Environment: WTP 1.0.1 + Geronimo 1.0 plugin + Geronimo 1.0 server
Reporter: Kathy Chan
Assignee: Sachin Patel
After creating a Web service using the Web service wizard on a Web project
targetting Geronimo server, the file server-config.wsdd is generated in the
server installation config-store directory under WAR name/WEB-INF.
However, if I change something in the EAR and republish, the
server-config.wsdd file is gone. Note that the server-config.wsdd file is
not in the workspace.
I am relying on the IModulePublishHelper.getPublishDirectory() API in the
org.eclipse.wst.server.core plugin to get the server's publish directory in
order to copy the server-config.wsdd file into the workspace so that next
time the WAR/EAR is re-published, the information of what was deployed to the
Axis servlet is persisted.
Tomcat is currently implementing that and Geronimo needs to implement
IModulePublishHelper.getPublishDirectory() as well.
Here's the current implementation in TomcatBehaviour.getPublishDirectory():
/**
* Returns the path that the module is
* published to when in test environment mode.
*
* @param module a module on the server
* @return the path that the module is published to when in test
environment mode,
*or null if not running as a test environment or the module is not
a web module
*/
public IPath getPublishDirectory(IModule[] module) {
if (!getTomcatServer().isTestEnvironment() || module == null ||
module.length != 1)
return null;
return
getTempDirectory().append(webapps).append(module[0].getName());
}
This solution would solve the problem for getting to server-config.wsdd for
Axis Web service but there is still a bigger general problem with files
created in the config-store directory not mirrored in the workspace.
Hopefully this will be addressed in the next release of the Geronimo plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-40) Cannot start server programmatically
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-40?page=comments#action_12369250 ] Kathy Chan commented on GERONIMODEVTOOLS-40: With Geronimo 1.0 server and Geronimo 1.0 plugin and WTP 1.0.1, after running through some scenarios to add EAR to server and starting and stopping server through the Web service scenario, I got into a state where even using server tooling to start the server would not return with the proper started state even when the server console indicated that Geronimo startup complete. Cannot start server programmatically Key: GERONIMODEVTOOLS-40 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-40 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Assignee: Sachin Patel Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin With a new workspace, do the following: - install Geronimo 1.0 server runtime - create Geronimo server using server tooling - start server - create Web project a1 with EAR - In the Web project, create a simple Echo.java with a hello method that takes a String and returns it. Here are the procedure to create a bottom-up Web service: - right-click on Echo.java, select Web Services - Create Web service - select test Web service and overwrite file on the 1st page of Web service wizard - click Finish - when the Web Services Explorer comes up, you should be able to invoke the hello method Now, if you remove the Web project a1 from the server and ensure that the server is still in started state, then you can repeat the above steps to create a bottom-up Web service. However, if you do not remove the Web project from the server first, then you'll run into the problem reported in bug http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39. If you remove the Web project from the server first but stop the server before creating the bottom-up Web service, when the Web service wizard tried to start the server programmatically, you'll notice that the server console indicates that Geronimo startup complete but server tooling still thinks that the server is started. The server start will eventually times out. Now, even if I use server tooling to start the server, server start would not complete. This problem persist even if I delete the server and recreate another one. The only way I could recover is to use a new workspace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-71) Geronimo publish failed with javax.naming.NoInitialContextException
Geronimo publish failed with javax.naming.NoInitialContextException --- Key: GERONIMODEVTOOLS-71 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-71 Project: Geronimo-Devtools Type: Bug Environment: WTP 1.0.1 + Geronimo 1.0 plugin + Geronimo 1.0 server Starting Eclipse with IBM JRE 1.4.2 J2RE 1.4.2 IBM Windows 32 build cn142-20050609 Reporter: Kathy Chan I had an EAR that's deployed to a Geronimo server. After I changed a Java file and re-publish to the server using server tooling popup menu on the server, I got the Publish Failed error. Here's the application console log: !SUBENTRY 1 org.apache.geronimo.devtools.eclipse.core 4 0 2006-03-07 13:08:59.630 !MESSAGE Connection to deployment manager failed. See .log for details. !STACK 0 javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: javax.naming.NoInitialCon textException: Cannot instantiate class: org.apache.naming.java.javaURLContextFactory [Root exceptio n is java.lang.ClassNotFoundException: org.apache.naming.java.javaURLContextFactory] at org.apache.geronimo.deployment.plugin.factories.DeploymentFactoryImpl.getDeploymentManage r(DeploymentFactoryImpl.java:132) at javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.getDeploymentManager(De ploymentFactoryManager.java:109) at org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManager(GeronimoConnectio nFactory.java:54) at org.apache.geronimo.core.commands.DeploymentCommandFactory.getDeploymentManager(Deploymen tCommandFactory.java:111) at org.apache.geronimo.core.commands.DeploymentCommandFactory.createRedeployCommand(Deployme ntCommandFactory.java:87) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.reDeploy(GeronimoServerBehaviou r.java:361) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doRedeploy(GeronimoServerBehavi our.java:282) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBeh aviour.java:234) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBeh aviour.java:217) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDe legate.java:672) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourD elegate.java:752) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate .java:610) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:800) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) Caused by: java.io.IOException: javax.naming.NoInitialContextException: Cannot instantiate class: or g.apache.naming.java.javaURLContextFactory [Root exception is java.lang.ClassNotFoundException: org. apache.naming.java.javaURLContextFactory] at mx4j.remote.resolver.rmi.Resolver.lookupStubInJNDI(Resolver.java:100) at mx4j.remote.resolver.rmi.Resolver.lookupRMIServerStub(Resolver.java:72) at mx4j.remote.resolver.rmi.Resolver.lookupClient(Resolver.java:52) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:119) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:38) at org.apache.geronimo.deployment.plugin.factories.DeploymentFactoryImpl.getDeploymentManage r(DeploymentFactoryImpl.java:125) at javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.getDeploymentManager(De ploymentFactoryManager.java:109) at org.apache.geronimo.core.GeronimoConnectionFactory.getDeploymentManager(GeronimoConnectio nFactory.java:54) at org.apache.geronimo.core.commands.DeploymentCommandFactory.getDeploymentManager(Deploymen tCommandFactory.java:111) at org.apache.geronimo.core.commands.DeploymentCommandFactory.createRedeployCommand(Deployme ntCommandFactory.java:87) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.reDeploy(GeronimoServerBehaviou r.java:361) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doRedeploy(GeronimoServerBehavi our.java:282) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBeh aviour.java:234) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBeh aviour.java:217) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDe legate.java:672) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourD elegate.java:752) at
[jira] Created: (GERONIMODEVTOOLS-73) Geronimo needs to support IModulePublishHelper.getPublishDirectory() to get to the server's publish directory
Geronimo needs to support IModulePublishHelper.getPublishDirectory() to get to
the server's publish directory
-
Key: GERONIMODEVTOOLS-73
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-73
Project: Geronimo-Devtools
Type: Bug
Environment: WTP 1.0.1 + Geronimo 1.0 plugin + Geronimo 1.0 server
Reporter: Kathy Chan
After creating a Web service using the Web service wizard on a Web project
targetting Geronimo server, the file server-config.wsdd is generated in the
server installation config-store directory under WAR name/WEB-INF. However,
if I change something in the EAR and republish, the server-config.wsdd file is
gone. Note that the server-config.wsdd file is not in the workspace.
I am relying on the IModulePublishHelper.getPublishDirectory() API in the
org.eclipse.wst.server.core plugin to get the server's publish directory in
order to copy the server-config.wsdd file into the workspace so that next time
the WAR/EAR is re-published, the information of what was deployed to the Axis
servlet is persisted.
Tomcat is currently implementing that and Geronimo needs to implement
IModulePublishHelper.getPublishDirectory() as well.
Here's the current implementation in TomcatBehaviour.getPublishDirectory():
/**
* Returns the path that the module is
* published to when in test environment mode.
*
* @param module a module on the server
* @return the path that the module is published to when in test
environment mode,
*or null if not running as a test environment or the module is not
a web module
*/
public IPath getPublishDirectory(IModule[] module) {
if (!getTomcatServer().isTestEnvironment() || module == null ||
module.length != 1)
return null;
return
getTempDirectory().append(webapps).append(module[0].getName());
}
This solution would solve the problem for getting to server-config.wsdd for
Axis Web service but there is still a bigger general problem with files created
in the config-store directory not mirrored in the workspace. Hopefully this
will be addressed in the next release of the Geronimo plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-72) Geronimo needs to support IModulePublishHelper.getPublishDirectory() to get to the server's publish directory
Geronimo needs to support IModulePublishHelper.getPublishDirectory() to get to
the server's publish directory
-
Key: GERONIMODEVTOOLS-72
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-72
Project: Geronimo-Devtools
Type: Bug
Environment: WTP 1.0.1 + Geronimo 1.0 plugin + Geronimo 1.0 server
Reporter: Kathy Chan
After creating a Web service using the Web service wizard on a Web project
targetting Geronimo server, the file server-config.wsdd is generated in the
server installation config-store directory under WAR name/WEB-INF. However,
if I change something in the EAR and republish, the server-config.wsdd file is
gone. Note that the server-config.wsdd file is not in the workspace.
I am relying on the IModulePublishHelper.getPublishDirectory() API in the
org.eclipse.wst.server.core plugin to get the server's publish directory in
order to copy the server-config.wsdd file into the workspace so that next time
the WAR/EAR is re-published, the information of what was deployed to the Axis
servlet is persisted.
Tomcat is currently implementing that and Geronimo needs to implement
IModulePublishHelper.getPublishDirectory() as well.
Here's the current implementation in TomcatBehaviour.getPublishDirectory():
/**
* Returns the path that the module is
* published to when in test environment mode.
*
* @param module a module on the server
* @return the path that the module is published to when in test
environment mode,
*or null if not running as a test environment or the module is not
a web module
*/
public IPath getPublishDirectory(IModule[] module) {
if (!getTomcatServer().isTestEnvironment() || module == null ||
module.length != 1)
return null;
return
getTempDirectory().append(webapps).append(module[0].getName());
}
This solution would solve the problem for getting to server-config.wsdd for
Axis Web service but there is still a bigger general problem with files created
in the config-store directory not mirrored in the workspace. Hopefully this
will be addressed in the next release of the Geronimo plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-72) Geronimo needs to support IModulePublishHelper.getPublishDirectory() to get to the server's publish directory
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-72?page=comments#action_12369307
]
Kathy Chan commented on GERONIMODEVTOOLS-72:
Please close this defect as
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-73 had been opened to
track this problem.
Geronimo needs to support IModulePublishHelper.getPublishDirectory() to get
to the server's publish directory
-
Key: GERONIMODEVTOOLS-72
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-72
Project: Geronimo-Devtools
Type: Bug
Environment: WTP 1.0.1 + Geronimo 1.0 plugin + Geronimo 1.0 server
Reporter: Kathy Chan
After creating a Web service using the Web service wizard on a Web project
targetting Geronimo server, the file server-config.wsdd is generated in the
server installation config-store directory under WAR name/WEB-INF.
However, if I change something in the EAR and republish, the
server-config.wsdd file is gone. Note that the server-config.wsdd file is
not in the workspace.
I am relying on the IModulePublishHelper.getPublishDirectory() API in the
org.eclipse.wst.server.core plugin to get the server's publish directory in
order to copy the server-config.wsdd file into the workspace so that next
time the WAR/EAR is re-published, the information of what was deployed to the
Axis servlet is persisted.
Tomcat is currently implementing that and Geronimo needs to implement
IModulePublishHelper.getPublishDirectory() as well.
Here's the current implementation in TomcatBehaviour.getPublishDirectory():
/**
* Returns the path that the module is
* published to when in test environment mode.
*
* @param module a module on the server
* @return the path that the module is published to when in test
environment mode,
*or null if not running as a test environment or the module is not
a web module
*/
public IPath getPublishDirectory(IModule[] module) {
if (!getTomcatServer().isTestEnvironment() || module == null ||
module.length != 1)
return null;
return
getTempDirectory().append(webapps).append(module[0].getName());
}
This solution would solve the problem for getting to server-config.wsdd for
Axis Web service but there is still a bigger general problem with files
created in the config-store directory not mirrored in the workspace.
Hopefully this will be addressed in the next release of the Geronimo plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-64) Tolerate projects or EARs without Geronimo facet.
Tolerate projects or EARs without Geronimo facet. - Key: GERONIMODEVTOOLS-64 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-64 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Driver: WTP M101 0207 and 0206 Geronimo plugins. If I add more then one EAR targetted to Geronimo runtime but do not add the Geronimo facet, then I get the error: !MESSAGE Configuration with id Application_IDalready exists. Existing configuration will be overwri tten with redeploy. Deployer operation failed: Could not parse application.xml org.apache.geronimo.common.DeploymentException: Could not parse application.xml at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:176 ) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.j ava:122) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke( generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor. java:96) at org.apache.geronimo.deployment.ConfigurationBuilder$$EnhancerByCGLIB$$6abab4ad.getDeploym entPlan(generated) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:219) Doing the same with Web project works beacuse the configID is falling back on the context root which will be uniquiq for all web projects in the workbench. I think the same defaulting should happen for EAR and other J2EE projects (other than Web project) so that adding the Geronimo facet is not required but just nice to have. This is especially important for code that programmatically create projects and EARs so that they are not required to add the default facet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-62) NPE in starting Geronimo server
NPE in starting Geronimo server --- Key: GERONIMODEVTOOLS-62 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-62 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Driver: WTP M200602070438 + Geronimo 0206_1658 plugins + Geronimo 1.0 server When going through bottom-up Web service scenario selecting to generate proxy and test Web service, the Geronimo server comes up with the following error in the console: Geronimo startup complete 11:27:42,031 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 11:28:08,879 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 11:28:55,627 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 11:28:55,787 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 11:29:03,798 WARN [TomcatModuleBuilder] Web application does not contain a WEB-INF/geronimo-web.xml deployment plan. This may or may not be a problem, depending on whether you have things like resource references that need to be resolved. You can also give the deployer a separate deployment plan file on the command line. 11:29:04,119 DEBUG [GBeanSingleReference] Waiting to start geronimo.server:J2EEApplication=Application_ID,J2EEServer=geronimo,j2eeType=WebModule,name=g2Client.war because no targets are running for reference J2EEApplication matching the patterns geronimo.server:J2EEServer=geronimo,j2eeType=J2EEApplication,name=Application_ID 11:29:04,129 INFO [StandardContext] Container org.apache.catalina.core.ContainerBase.[/g2Client] has not been started 11:29:04,129 ERROR [GBeanInstance] Problem in doFail of geronimo.server:J2EEApplication=Application_ID,J2EEServer=geronimo,j2eeType=WebModule,name=g2Client.war java.lang.NullPointerException at org.apache.geronimo.tomcat.TomcatContainer.removeContext(TomcatContainer.java:305) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$9f00ee94.removeContext(generated) at org.apache.geronimo.tomcat.TomcatWebAppContext.doFail(TomcatWebAppContext.java:424) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:955) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:325) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:110) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:520) at org.apache.geronimo.gbean.runtime.GBeanSingleReference.attemptFullStart(GBeanSingleReference.java:154) at org.apache.geronimo.gbean.runtime.GBeanSingleReference.targetAdded(GBeanSingleReference.java:127) at org.apache.geronimo.gbean.runtime.AbstractGBeanReference.addTarget(AbstractGBeanReference.java:242) at org.apache.geronimo.gbean.runtime.GBeanSingleReference$1.running(GBeanSingleReference.java:163) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:155) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:38) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:231) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:350) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:110) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:132) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:537) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:208) at
[jira] Commented: (GERONIMODEVTOOLS-40) Cannot start server programmatically
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-40?page=comments#action_12365469 ] Kathy Chan commented on GERONIMODEVTOOLS-40: I retried creating Web service on Geronimo server using WTP M02070438 and the 0206 Geronimo plugin. I still hit the problem of Geronimo server reported to be still starting when it had actually been started. When this happened, I checked the server port and they are set. The problem seems to be intermittent. Cannot start server programmatically Key: GERONIMODEVTOOLS-40 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-40 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Assignee: Sachin Patel Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin With a new workspace, do the following: - install Geronimo 1.0 server runtime - create Geronimo server using server tooling - start server - create Web project a1 with EAR - In the Web project, create a simple Echo.java with a hello method that takes a String and returns it. Here are the procedure to create a bottom-up Web service: - right-click on Echo.java, select Web Services - Create Web service - select test Web service and overwrite file on the 1st page of Web service wizard - click Finish - when the Web Services Explorer comes up, you should be able to invoke the hello method Now, if you remove the Web project a1 from the server and ensure that the server is still in started state, then you can repeat the above steps to create a bottom-up Web service. However, if you do not remove the Web project from the server first, then you'll run into the problem reported in bug http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39. If you remove the Web project from the server first but stop the server before creating the bottom-up Web service, when the Web service wizard tried to start the server programmatically, you'll notice that the server console indicates that Geronimo startup complete but server tooling still thinks that the server is started. The server start will eventually times out. Now, even if I use server tooling to start the server, server start would not complete. This problem persist even if I delete the server and recreate another one. The only way I could recover is to use a new workspace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMODEVTOOLS-56) URLProvider.getModuleRootURL() returning WebApp_ID
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-56?page=all ] Kathy Chan closed GERONIMODEVTOOLS-56: -- Verified on WTP M101 02070438 and Geronimo plugin 0206. URLProvider.getModuleRootURL() returning WebApp_ID Key: GERONIMODEVTOOLS-56 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-56 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Assignee: Sachin Patel Driver: - WTP 1.0.1 M20060131_1015, - Geronimo Server 1.0, - Geronimo plugin 0130_0958 For a Web project called g1Client, the context root is return as WebApp_ID rather than g1Client. Here's the code: IURLProvider urlProvider = (IURLProvider) serverInstance.loadAdapter(IURLProvider.class, null); URL url = urlProvider.getModuleRootURL(module); url is returned as: http://localhost:8080/WebApp_ID/ I was expecting: http://localhost:8080/g1Client/ The problem can easily be reproduced by going through a Web Service Client scenario with test Web service. Notice that the URL for the TestClient is wrong, it should be: http://localhost:8080/g1Client/sampleEchoProxy/TestClient.jsp rather than the current URL: http://localhost:8080/WebApp_ID/sampleEchoProxy/TestClient.jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-62) NPE in starting Geronimo server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-62?page=comments#action_12365480 ] Kathy Chan commented on GERONIMODEVTOOLS-62: I can easily reproduce the problem by just creating a server using the server tooling wizard, starts it and then restarts it. NPE in starting Geronimo server --- Key: GERONIMODEVTOOLS-62 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-62 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Driver: WTP M200602070438 + Geronimo 0206_1658 plugins + Geronimo 1.0 server When going through bottom-up Web service scenario selecting to generate proxy and test Web service, the Geronimo server comes up with the following error in the console: Geronimo startup complete 11:27:42,031 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 11:28:08,879 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 11:28:55,627 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 11:28:55,787 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 11:29:03,798 WARN [TomcatModuleBuilder] Web application does not contain a WEB-INF/geronimo-web.xml deployment plan. This may or may not be a problem, depending on whether you have things like resource references that need to be resolved. You can also give the deployer a separate deployment plan file on the command line. 11:29:04,119 DEBUG [GBeanSingleReference] Waiting to start geronimo.server:J2EEApplication=Application_ID,J2EEServer=geronimo,j2eeType=WebModule,name=g2Client.war because no targets are running for reference J2EEApplication matching the patterns geronimo.server:J2EEServer=geronimo,j2eeType=J2EEApplication,name=Application_ID 11:29:04,129 INFO [StandardContext] Container org.apache.catalina.core.ContainerBase.[/g2Client] has not been started 11:29:04,129 ERROR [GBeanInstance] Problem in doFail of geronimo.server:J2EEApplication=Application_ID,J2EEServer=geronimo,j2eeType=WebModule,name=g2Client.war java.lang.NullPointerException at org.apache.geronimo.tomcat.TomcatContainer.removeContext(TomcatContainer.java:305) at org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$9f00ee94.removeContext(generated) at org.apache.geronimo.tomcat.TomcatWebAppContext.doFail(TomcatWebAppContext.java:424) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:955) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:325) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:110) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:520) at org.apache.geronimo.gbean.runtime.GBeanSingleReference.attemptFullStart(GBeanSingleReference.java:154) at org.apache.geronimo.gbean.runtime.GBeanSingleReference.targetAdded(GBeanSingleReference.java:127) at org.apache.geronimo.gbean.runtime.AbstractGBeanReference.addTarget(AbstractGBeanReference.java:242) at org.apache.geronimo.gbean.runtime.GBeanSingleReference$1.running(GBeanSingleReference.java:163) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:155) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:38) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:231) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:350) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:110) at
[jira] Created: (GERONIMODEVTOOLS-56) URLProvider.getModuleRootURL() returning WebApp_ID
URLProvider.getModuleRootURL() returning WebApp_ID Key: GERONIMODEVTOOLS-56 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-56 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Driver: - WTP 1.0.1 M20060131_1015, - Geronimo Server 1.0, - Geronimo plugin 0130_0958 For a Web project called g1Client, the context root is return as WebApp_ID rather than g1Client. Here's the code: IURLProvider urlProvider = (IURLProvider) serverInstance.loadAdapter(IURLProvider.class, null); URL url = urlProvider.getModuleRootURL(module); url is returned as: http://localhost:8080/WebApp_ID/ I was expecting: http://localhost:8080/g1Client/ The problem can easily be reproduced by going through a Web Service Client scenario with test Web service. Notice that the URL for the TestClient is wrong, it should be: http://localhost:8080/g1Client/sampleEchoProxy/TestClient.jsp rather than the current URL: http://localhost:8080/WebApp_ID/sampleEchoProxy/TestClient.jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMODEVTOOLS-45) NPE when publishing to Geronimo server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-45?page=all ] Kathy Chan closed GERONIMODEVTOOLS-45: -- Verified on Geronimo plugin 0130_0958. NPE when publishing to Geronimo server -- Key: GERONIMODEVTOOLS-45 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-45 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Assignee: Sachin Patel Priority: Critical Driver used: WTP 1.0, Geronimo 1.0 server, Geronimo 01/09 plugins After installing Geronimo server runtime and creating a Geronimo server using WTP (there's no other project or EAR on the server): - New -Web Services - Web Service client - Click Next - On the Web Service selection page, paste the following in the URI field at the top of the page: http://www.xmethods.net/sd/2001/CurrencyExchangeService.wsdl - Click Next. - In the Client Environment Configuration page, enter a name for a new Web project and EAR project. The Web service runtime should be Apache Axis and server should be Apache Geronimo 1.0. - Click Finish would result in: Publishing failed Could not publish to the server. java.lang.NullPointerException at org.apache.geronimo.core.commands.DeploymentCmdStatus.isOK(DeploymentCmdStatus.java:115) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doRedeploy(GeronimoServerBehaviour.java:249) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:204) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:188) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand$1.run(StartServerCommand.java:185) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-40) Cannot start server programmatically
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-40?page=comments#action_12364675 ] Kathy Chan commented on GERONIMODEVTOOLS-40: I just tried WTP M101 20060131_1015 with Geronimo plugin 0130_0958. I was able to use the Web service wizard to create a Geronimo server and start it programmatically. I was able to deploy multiple services to the same started server. However once I stop the Geronimo server, it could not be started (the console would show Geronimo startup complete but server status still shows starting). After the problem occurs, I would get the same problem if I stop the server, delete the server and tried to start the Geronimo server using server tooling. So it looks like part of the problem is fixed but there are still problems with start server. Please reopen the defect. Cannot start server programmatically Key: GERONIMODEVTOOLS-40 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-40 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Assignee: Sachin Patel Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin With a new workspace, do the following: - install Geronimo 1.0 server runtime - create Geronimo server using server tooling - start server - create Web project a1 with EAR - In the Web project, create a simple Echo.java with a hello method that takes a String and returns it. Here are the procedure to create a bottom-up Web service: - right-click on Echo.java, select Web Services - Create Web service - select test Web service and overwrite file on the 1st page of Web service wizard - click Finish - when the Web Services Explorer comes up, you should be able to invoke the hello method Now, if you remove the Web project a1 from the server and ensure that the server is still in started state, then you can repeat the above steps to create a bottom-up Web service. However, if you do not remove the Web project from the server first, then you'll run into the problem reported in bug http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39. If you remove the Web project from the server first but stop the server before creating the bottom-up Web service, when the Web service wizard tried to start the server programmatically, you'll notice that the server console indicates that Geronimo startup complete but server tooling still thinks that the server is started. The server start will eventually times out. Now, even if I use server tooling to start the server, server start would not complete. This problem persist even if I delete the server and recreate another one. The only way I could recover is to use a new workspace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMODEVTOOLS-39) Publishing failed with Module Application_ID already exists in the server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39?page=all ] Kathy Chan closed GERONIMODEVTOOLS-39: -- Verified on Geronimo plugin 0130_0958. Publishing failed with Module Application_ID already exists in the server - Key: GERONIMODEVTOOLS-39 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Assignee: Sachin Patel Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin With a new workspace, do the following: - install Geronimo 1.0 server runtime - create Geronimo server using server tooling - start server - create hello.html in Web project a1. Run on server. - create hello.html in Web project a2. Run on server. You'll get the error: Publishing failed Distribution of configuration failed. See .log for details. java.lang.Exception: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:235) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.invoke(MBeanServerDelegate.java:117) at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219) at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31) at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:500) at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80) at $Proxy0.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:221) at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doFail(GeronimoServerBehaviour.java:279) at
[jira] Closed: (GERONIMODEVTOOLS-19) Cannot create Web project targetting Geronimo using WTP M9
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-19?page=all ] Kathy Chan closed GERONIMODEVTOOLS-19: -- Not a problem with Geronimo plugin 0130_0958. Cannot create Web project targetting Geronimo using WTP M9 -- Key: GERONIMODEVTOOLS-19 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-19 Project: Geronimo-Devtools Type: Bug Environment: Windows 2000 Reporter: Kathy Chan Assignee: Sachin Patel Priority: Critical Using WTP 1116_2235 driver and Geronimo plugin and Geronimo server zip from Sachin Patel, I was not able to create a dynamic Web project targetting Geronimo. It's likely that the server runtime/facet mapping had not been defined in the Geronimo plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-46) ClassNotFound when running
ClassNotFound when running --- Key: GERONIMODEVTOOLS-46 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-46 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Driver: - WTP 1.0 - Geronimo 1.0 server - Geronimo 01/11 plugins Launch Eclipse with JDK1.5.0_04, new workspace: - install Geronimo server runtime using jdk142_09 - create f1 with f1EAR - add Geronimo facet to f1EAR manually - create Geronimo server, start server - create hello.html on f1, run on server Error: Publishing failed Starting of configuration failed. See .log for details. java.lang.Exception: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: org.apache.geronimo.kernel.GBeanNotFoundException (no security manager: RMI class loader disabled) java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: org.apache.geronimo.kernel.GBeanNotFoundException (no security manager: RMI class loader disabled) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:217) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:969) at org.apache.geronimo.kernel.jmx.KernelDelegate.invokeKernel(KernelDelegate.java:339) at org.apache.geronimo.kernel.jmx.KernelDelegate.getGBeanState(KernelDelegate.java:121) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:64) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.ClassNotFoundException: org.apache.geronimo.kernel.GBeanNotFoundException (no security manager: RMI class loader disabled) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:371) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165) at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620) at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247) at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1538) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215) ... 8 more at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doFail(GeronimoServerBehaviour.java:279) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:235) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:200) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:188) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) The problem do not occur if I run Eclipse with JDK 1.4.2_09. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMODEVTOOLS-46) ClassNotFound when publishing to Geronimo when Eclipse is launched with JDK1.5
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-46?page=all ] Kathy Chan updated GERONIMODEVTOOLS-46: --- Summary: ClassNotFound when publishing to Geronimo when Eclipse is launched with JDK1.5 (was: ClassNotFound when running) ClassNotFound when publishing to Geronimo when Eclipse is launched with JDK1.5 -- Key: GERONIMODEVTOOLS-46 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-46 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Driver: - WTP 1.0 - Geronimo 1.0 server - Geronimo 01/11 plugins Launch Eclipse with JDK1.5.0_04, new workspace: - install Geronimo server runtime using jdk142_09 - create f1 with f1EAR - add Geronimo facet to f1EAR manually - create Geronimo server, start server - create hello.html on f1, run on server Error: Publishing failed Starting of configuration failed. See .log for details. java.lang.Exception: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: org.apache.geronimo.kernel.GBeanNotFoundException (no security manager: RMI class loader disabled) java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: org.apache.geronimo.kernel.GBeanNotFoundException (no security manager: RMI class loader disabled) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:217) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:969) at org.apache.geronimo.kernel.jmx.KernelDelegate.invokeKernel(KernelDelegate.java:339) at org.apache.geronimo.kernel.jmx.KernelDelegate.getGBeanState(KernelDelegate.java:121) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:64) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.ClassNotFoundException: org.apache.geronimo.kernel.GBeanNotFoundException (no security manager: RMI class loader disabled) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:371) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165) at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620) at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247) at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1538) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215) ... 8 more at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doFail(GeronimoServerBehaviour.java:279) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:235) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:200) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:188) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) The problem do not occur if I run Eclipse with JDK 1.4.2_09. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators:
[jira] Commented: (GERONIMODEVTOOLS-45) NPE when publishing to Geronimo server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-45?page=comments#action_12362543 ] Kathy Chan commented on GERONIMODEVTOOLS-45: Actually, there's an even easier way to reproduce the problem: - install Geronimo runtime - Create Web project g2 targeting Geronimo, select add to g2EAR - Create a HTML file, select Run on Server on the file - You'll first get the error: java.lang.Exception: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:235) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.invoke(MBeanServerDelegate.java:117) at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219) at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31) at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:500) at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80) at $Proxy0.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:221) at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doFail(GeronimoServerBehaviour.java:279) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:224) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:200) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:188) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596) at
[jira] Closed: (GERONIMODEVTOOLS-37) Spec JARs missing in Geronimo targetted Web project
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-37?page=all ] Kathy Chan closed GERONIMODEVTOOLS-37: -- Verified on the 01/11 Geronimo plugin. Spec JARs missing in Geronimo targetted Web project --- Key: GERONIMODEVTOOLS-37 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-37 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Assignee: Sachin Patel Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin After installing Geronimo server runtime, I was able to create a Geronimo server, create a Web project targeting Geronimo, start the server and publish a HTML file on the Web project. However, when I tried to create a servlet in the Web project, the servlet class does not compile because the javax.servlet classes cannot be resolved. I did a search on the Web and found that those classes are contained in the following JARs: - geronimo-spec-servlet-2.4-rc4.jar - geronimo-spec-j2ee-1.4-rc3.jar However, those JARs are not in the Geronimo 1.0 server lib directory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-39) Publishing failed with Module Application_ID already exists in the server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39?page=comments#action_12362551 ] Kathy Chan commented on GERONIMODEVTOOLS-39: I tried to work around the problem by adding the Geronimo facet to the EAR using the project properties pop-up. It did not work and returned with the error: java.lang.Exception: Module g1EAR/g1EAR already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module g1EAR/g1EAR already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:235) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.invoke(MBeanServerDelegate.java:117) at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219) at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31) at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:500) at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80) at $Proxy0.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:221) at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doFail(GeronimoServerBehaviour.java:279) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:224) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:200) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:188) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:799) at
[jira] Commented: (GERONIMODEVTOOLS-39) Publishing failed with Module Application_ID already exists in the server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39?page=comments#action_12362553 ] Kathy Chan commented on GERONIMODEVTOOLS-39: Note that the problem with Publishing failed with Module Application_ID already exists in the server - Key: GERONIMODEVTOOLS-39 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin With a new workspace, do the following: - install Geronimo 1.0 server runtime - create Geronimo server using server tooling - start server - create hello.html in Web project a1. Run on server. - create hello.html in Web project a2. Run on server. You'll get the error: Publishing failed Distribution of configuration failed. See .log for details. java.lang.Exception: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:235) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.invoke(MBeanServerDelegate.java:117) at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219) at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31) at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:500) at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80) at $Proxy0.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:221) at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doFail(GeronimoServerBehaviour.java:279) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doDeploy(GeronimoServerBehaviour.java:224) at
[jira] Commented: (GERONIMODEVTOOLS-39) Publishing failed with Module Application_ID already exists in the server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39?page=comments#action_12362557 ] Kathy Chan commented on GERONIMODEVTOOLS-39: Note that the problem with java.lang.Exception: Module g1EAR/g1EAR already exists in the server. Try to undeploy it first or use the redeploy command. only occurs if the server does not exist and I use Run on server to try to bring up the HTML file. It does not always happen if I create the server first before Run on Server. Publishing failed with Module Application_ID already exists in the server - Key: GERONIMODEVTOOLS-39 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin With a new workspace, do the following: - install Geronimo 1.0 server runtime - create Geronimo server using server tooling - start server - create hello.html in Web project a1. Run on server. - create hello.html in Web project a2. Run on server. You'll get the error: Publishing failed Distribution of configuration failed. See .log for details. java.lang.Exception: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:235) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.invoke(MBeanServerDelegate.java:117) at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219) at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31) at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:500) at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80) at $Proxy0.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:221) at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at
[jira] Commented: (GERONIMODEVTOOLS-45) NPE when publishing to Geronimo server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-45?page=comments#action_12362563 ] Kathy Chan commented on GERONIMODEVTOOLS-45: Just want to clarify that I had add Geronimo facet to the EAR when I still ran into this problem. Please let me know if you still have problem reproducing the error. NPE when publishing to Geronimo server -- Key: GERONIMODEVTOOLS-45 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-45 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Priority: Critical Driver used: WTP 1.0, Geronimo 1.0 server, Geronimo 01/09 plugins After installing Geronimo server runtime and creating a Geronimo server using WTP (there's no other project or EAR on the server): - New -Web Services - Web Service client - Click Next - On the Web Service selection page, paste the following in the URI field at the top of the page: http://www.xmethods.net/sd/2001/CurrencyExchangeService.wsdl - Click Next. - In the Client Environment Configuration page, enter a name for a new Web project and EAR project. The Web service runtime should be Apache Axis and server should be Apache Geronimo 1.0. - Click Finish would result in: Publishing failed Could not publish to the server. java.lang.NullPointerException at org.apache.geronimo.core.commands.DeploymentCmdStatus.isOK(DeploymentCmdStatus.java:115) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doRedeploy(GeronimoServerBehaviour.java:249) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:204) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:188) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand$1.run(StartServerCommand.java:185) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-45) NPE when publishing to Geronimo server
NPE when publishing to Geronimo server -- Key: GERONIMODEVTOOLS-45 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-45 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Priority: Critical Driver used: WTP 1.0, Geronimo 1.0 server, Geronimo 01/09 plugins After installing Geronimo server runtime and creating a Geronimo server using WTP (there's no other project or EAR on the server): - New -Web Services - Web Service client - Click Next - On the Web Service selection page, paste the following in the URI field at the top of the page: http://www.xmethods.net/sd/2001/CurrencyExchangeService.wsdl - Click Next. - In the Client Environment Configuration page, enter a name for a new Web project and EAR project. The Web service runtime should be Apache Axis and server should be Apache Geronimo 1.0. - Click Finish would result in: Publishing failed Could not publish to the server. java.lang.NullPointerException at org.apache.geronimo.core.commands.DeploymentCmdStatus.isOK(DeploymentCmdStatus.java:115) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doRedeploy(GeronimoServerBehaviour.java:249) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:204) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:188) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand$1.run(StartServerCommand.java:185) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-45) NPE when publishing to Geronimo server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-45?page=comments#action_12362493 ] Kathy Chan commented on GERONIMODEVTOOLS-45: Just want to clarify the steps: - New -Web Services - Web Service client - Click Next - On the first page (Web Service Client page), select Test Web service and overwrite. After the Web Service client wizard encounters the publish error, click OK on the publish fail error and click Cancel from the Web Service client wizard. Now the new Web project had been added to the server. Attempting to start the server would result in the same publish fail error. However, even after I remove the Web project from the server, I still would get the publish fail error. The error only disappears if I delete the server and restart it. NPE when publishing to Geronimo server -- Key: GERONIMODEVTOOLS-45 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-45 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Priority: Critical Driver used: WTP 1.0, Geronimo 1.0 server, Geronimo 01/09 plugins After installing Geronimo server runtime and creating a Geronimo server using WTP (there's no other project or EAR on the server): - New -Web Services - Web Service client - Click Next - On the Web Service selection page, paste the following in the URI field at the top of the page: http://www.xmethods.net/sd/2001/CurrencyExchangeService.wsdl - Click Next. - In the Client Environment Configuration page, enter a name for a new Web project and EAR project. The Web service runtime should be Apache Axis and server should be Apache Geronimo 1.0. - Click Finish would result in: Publishing failed Could not publish to the server. java.lang.NullPointerException at org.apache.geronimo.core.commands.DeploymentCmdStatus.isOK(DeploymentCmdStatus.java:115) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.doRedeploy(GeronimoServerBehaviour.java:249) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.invokeCommand(GeronimoServerBehaviour.java:204) at org.apache.geronimo.core.internal.GeronimoServerBehaviour.publishModule(GeronimoServerBehaviour.java:188) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:799) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:788) at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand$1.run(StartServerCommand.java:185) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-39) Publishing failed with Module Application_ID already exists in the server
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39?page=comments#action_12362498 ] Kathy Chan commented on GERONIMODEVTOOLS-39: I found that if I created 2 Web projects g1 and g2 targetting Geronimo, the web.xml has web-app id=WebApp_ID version=2.4 xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd; for both. However, the config id in geronimo-web.xml is properly set to configId=g1/g1 and g2/g2. So the problem did not occur if the Web projects are not in EARs. The problem only occurs if the Web project are in EARs since the application.xml contains: application id=Application_ID version=1.4 xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd; for both and geronimo-app.xml is missing (there's a WTP bug on the Geronimo Deployment Plan facet only got ran against the web project and not the ear project). Sachin, what's the WTP bug number? Publishing failed with Module Application_ID already exists in the server - Key: GERONIMODEVTOOLS-39 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin With a new workspace, do the following: - install Geronimo 1.0 server runtime - create Geronimo server using server tooling - start server - create hello.html in Web project a1. Run on server. - create hello.html in Web project a2. Run on server. You'll get the error: Publishing failed Distribution of configuration failed. See .log for details. java.lang.Exception: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. org.apache.geronimo.common.DeploymentException: Module Application_ID already exists in the server. Try to undeploy it first or use the redeploy command. at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:235) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:102) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:125) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) at org.apache.geronimo.kernel.jmx.MBeanServerDelegate.invoke(MBeanServerDelegate.java:117) at mx4j.remote.rmi.RMIConnectionInvoker.invoke(RMIConnectionInvoker.java:219) at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at mx4j.remote.rmi.RMIConnectionProxy.invoke(RMIConnectionProxy.java:34) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.chain(RMIConnectionSubjectInvoker.java:99) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.access$000(RMIConnectionSubjectInvoker.java:31) at mx4j.remote.rmi.RMIConnectionSubjectInvoker$1.run(RMIConnectionSubjectInvoker.java:90) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:500) at mx4j.remote.MX4JRemoteUtils.subjectInvoke(MX4JRemoteUtils.java:163) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.subjectInvoke(RMIConnectionSubjectInvoker.java:86) at mx4j.remote.rmi.RMIConnectionSubjectInvoker.invoke(RMIConnectionSubjectInvoker.java:80) at $Proxy0.invoke(Unknown Source) at
[jira] Created: (GERONIMODEVTOOLS-37) Spec JARs missing in Geronimo targetted Web project
Spec JARs missing in Geronimo targetted Web project --- Key: GERONIMODEVTOOLS-37 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-37 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows XP Reporter: Kathy Chan Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin After installing Geronimo server runtime, I was able to create a Geronimo server, create a Web project targeting Geronimo, start the server and publish a HTML file on the Web project. However, when I tried to create a servlet in the Web project, the servlet class does not compile because the javax.servlet classes cannot be resolved. I did a search on the Web and found that those classes are contained in the following JARs: - geronimo-spec-servlet-2.4-rc4.jar - geronimo-spec-j2ee-1.4-rc3.jar However, those JARs are not in the Geronimo 1.0 server lib directory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-40) Cannot start server programmatically
Cannot start server programmatically Key: GERONIMODEVTOOLS-40 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-40 Project: Geronimo-Devtools Type: Bug Environment: Windows XP Reporter: Kathy Chan Priority: Critical I was using the following drivers on Windows XP: - WTP 1.0 - Geronimo 1.0 server - Geronimo 20060109 plugin With a new workspace, do the following: - install Geronimo 1.0 server runtime - create Geronimo server using server tooling - start server - create Web project a1 with EAR - In the Web project, create a simple Echo.java with a hello method that takes a String and returns it. Here are the procedure to create a bottom-up Web service: - right-click on Echo.java, select Web Services - Create Web service - select test Web service and overwrite file on the 1st page of Web service wizard - click Finish - when the Web Services Explorer comes up, you should be able to invoke the hello method Now, if you remove the Web project a1 from the server and ensure that the server is still in started state, then you can repeat the above steps to create a bottom-up Web service. However, if you do not remove the Web project from the server first, then you'll run into the problem reported in bug http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39. If you remove the Web project from the server first but stop the server before creating the bottom-up Web service, when the Web service wizard tried to start the server programmatically, you'll notice that the server console indicates that Geronimo startup complete but server tooling still thinks that the server is started. The server start will eventually times out. Now, even if I use server tooling to start the server, server start would not complete. This problem persist even if I delete the server and recreate another one. The only way I could recover is to use a new workspace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-19) Cannot create Web project targetting Geronimo using WTP M9
Cannot create Web project targetting Geronimo using WTP M9 -- Key: GERONIMODEVTOOLS-19 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-19 Project: Geronimo-Devtools Type: Bug Environment: Windows 2000 Reporter: Kathy Chan Priority: Critical Using WTP 1116_2235 driver and Geronimo plugin and Geronimo server zip from Sachin Patel, I was not able to create a dynamic Web project targetting Geronimo. It's likely that the server runtime/facet mapping had not been defined in the Geronimo plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
