[JBoss Tools (users)] - Failed to generate implementation class
by soa2008
Hello!
By trying to generate Java skeleton code from my WSDL, I get an exception:
Failed to generate implementation class
org.eclipse.core.runtime.CoreException: Failed to Generate Web Service code, please check the log for more details
at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.getCompilationUnitForInterface(ImplementationClassCreationCommand.java:438)
at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.generateImplClass(ImplementationClassCreationCommand.java:123)
at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.execute(ImplementationClassCreationCommand.java:98)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.performFinish(WizardPageManager.java:262)
at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.performFinish(DynamicWizard.java:382)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
------------------------------------------------------
Tell me please where can be my mistake?
Eclipse 3.4.2
JBoss 5.0.1 (can start)
create a Dynamic Web project:
target runtime: jboss server 5.0
Dynamic Web Module:2.5
set the project facet:
add JBoss Web Services facet, select the checkbox of Server Supplied JBossWS Runtime in the JBossWS wizard
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216313#4216313
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216313
15 years, 10 months
[JCA/JBoss] - Re: ConnectionCount and InUseConnectionCount behavior
by PeterJ
The ConnectionCount is the total number of connections that have been established since JBoss AS started. Consider this scenario. An app accesses the database so 5 connections (min-pool-size) are created. Then the app gets busy and it needs more connections, let's say a total of 20 connections. At this point both InUseConnectionCount and ConnectionCount are 20. The the app is no longer busy, so after 5 minutes (idle-timeout-minutes) the number of connections in use (InUseConnectionCount) goes back down to 5. At this point ConnectionCount is still 20. Later the app gets busy again and let's assume that 25 connections are required. Thus 20 new connections were created. At this point ConnectionCount is 40 and InUseConnectionCount is 25. Then the app is no longer busy and those connections are no longer needed, so the InUseConnectionCount goes back down to 5. But ConnectionCount is still at 40.
Hope this helps.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216308#4216308
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216308
15 years, 10 months
[JCA/JBoss] - ConnectionCount and InUseConnectionCount behavior
by jguser
Hello,
I have a doubt in the behavior of the connection pool of the Jboss.
We are using JBoss 4.0.2 with java version "1.5.0_10"
I'm trying to understand the behavior of the ConnectionCount in relation with the InUseConnectionCount, and it seems like the JBoss create connections that he don't realy use.
I'm being looking in the source of JBoss to understand this but I can't find much about it.
Our datasource configuration is:
<local-tx-datasource>
<jndi-name>XXXXXXX</jndi-name>
<connection-url>XXXXXXX</connection-url>
<driver-class>XXXXXXX</driver-class>
<user-name>XXXXXXX</user-name>
XXXXXXX
<min-pool-size>5</min-pool-size>
<max-pool-size>40</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
<check-valid-connection-sql>some valid sql select</check-valid-connection-sql>
</local-tx-datasource>
For example, a common behavior of one normal day, sometimes we have 40 ConnectionCount (the max-pool configurated) where is only 5 InUseConnection.
We have a average of a 16.88 of difference between de ConnectionCount and InUseConnectionCount
Anyone can tell me wich is the behavior of the connection pool?? When he creates new connection that re don't realy needs?
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216304#4216304
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216304
15 years, 10 months