[JBoss Tools] - Trouble while installing Jboss tools 3.3 on Eclipse 3.7 sr2
by vjosh
vjosh [https://community.jboss.org/people/vjosh] created the document:
"Trouble while installing Jboss tools 3.3 on Eclipse 3.7 sr2"
To view the document, visit: https://community.jboss.org/docs/DOC-28772
--------------------------------------------------------------
i have download eclipse-jee-indigo-SR2-win32 from eclipse.org.
then i followe the instructions on the given link http://www.jboss.org/tools/download/installation/update_3_3 http://www.jboss.org/tools/download/installation/update_3_3
there is a instruction to install it via eclipse marketplace or via http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/ this update site url.
but while installing the hibernate plugin of jboss tools it is giving me error irrespective of the way mentioned above.
even i tried url given below
http://download.jboss.org/jbosstools/updates/stable/indigo http://download.jboss.org/jbosstools/updates/stable/indigo but still the same result
the error is given below
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,org.hibernate.eclipse.console,3.5.1.v20120715-0252-H98-Final.
MD5 hash is not as expected. Expected: 2b8a871d38aeb31ca6cab8dc99111be4 and found f41b048b4096cc37861345db0af869d0.
Problems downloading artifact: osgi.bundle,org.hibernate.eclipse.libs,3.5.1.v20120715-0252-H98-Final.
MD5 hash is not as expected. Expected: a309dd0dd94745c134bb9642390ac8ce and found 32088742fff821725e541b31c08acf20.
Problems downloading artifact: osgi.bundle,org.jboss.tools.hibernate4_0,3.5.1.v20120715-0252-H98-Final.
MD5 hash is not as expected. Expected: b80c07dc002685655bbb0763374b6a12 and found fdcfb2555a56ee14df91e753bf848690.
i want to install hibernate plug-in for the development work on priority basis.
*could someone please shed some light as to why this error has come ?*
is there a problem with jdk, eclipse or jboss url ?
i am using jdk 6 update34
can somebody guide me as to where is the issue here?
reply is awaited on ASAP basis.
Thanks In Advance...........
This article was generated from the following discussion: https://community.jboss.org/thread/205003 Trouble while installing Jboss tools 3.3 on Eclipse 3.7 sr2
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-28772]
Create a new document in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
11 years, 8 months
[JBoss Tools] - Trouble while installing Jboss tools 3.3 on Eclipse 3.7 sr2
by vjosh
vjosh [https://community.jboss.org/people/vjosh] created the discussion
"Trouble while installing Jboss tools 3.3 on Eclipse 3.7 sr2"
To view the discussion, visit: https://community.jboss.org/message/758188#758188
--------------------------------------------------------------
i have download eclipse-jee-indigo-SR2-win32 from eclipse.org.
then i followe the instructions on the given link http://www.jboss.org/tools/download/installation/update_3_3 http://www.jboss.org/tools/download/installation/update_3_3
there is a instruction to install it via eclipse marketplace or via http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/ this update site url.
but while installing the hibernate plugin of jboss tools it is giving me error irrespective of the way mentioned above.
even i tried url given below
http://download.jboss.org/jbosstools/updates/stable/indigo http://download.jboss.org/jbosstools/updates/stable/indigo but still the same result
the error is given below
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,org.hibernate.eclipse.console,3.5.1.v20120715-0252-H98-Final.
MD5 hash is not as expected. Expected: 2b8a871d38aeb31ca6cab8dc99111be4 and found f41b048b4096cc37861345db0af869d0.
Problems downloading artifact: osgi.bundle,org.hibernate.eclipse.libs,3.5.1.v20120715-0252-H98-Final.
MD5 hash is not as expected. Expected: a309dd0dd94745c134bb9642390ac8ce and found 32088742fff821725e541b31c08acf20.
Problems downloading artifact: osgi.bundle,org.jboss.tools.hibernate4_0,3.5.1.v20120715-0252-H98-Final.
MD5 hash is not as expected. Expected: b80c07dc002685655bbb0763374b6a12 and found fdcfb2555a56ee14df91e753bf848690.
i want to install hibernate plug-in for the development work on priority basis.
*could someone please shed some light as to why this error has come ?*
is there a problem with jdk, eclipse or jboss url ?
i am using jdk 6 update34
can somebody guide me as to where is the issue here?
reply is awaited on ASAP basis.
Thanks In Advance...........
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/758188#758188]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 8 months
[JBoss Cache] - Error while trying to acquire write lock
by Túlio Gomes Barbosa
Túlio Gomes Barbosa [https://community.jboss.org/people/tulio.barbosa] created the discussion
"Error while trying to acquire write lock"
To view the discussion, visit: https://community.jboss.org/message/757029#757029
--------------------------------------------------------------
Hi guys,
i'm a brazilian oss analyst facing with the following problem:
<Aug 28, 2012 10:15:22 AM BRT> <Notice> <Stdout> <BEA-000000> <AsyncClient: Response cannot be read!>
<8-28-2012 10:15:22.261> <JVMDAgent|jamagent.c:1472> <Error receiving data from console>
<Aug 28, 2012 10:15:32 AM BRT> <Notice> <Stdout> <BEA-000000> <<28-Aug-2012 10:15:32,483 BRT AM> <ERROR> <jboss.JBossOrderCacheManager> <ExecuteThread: '12'
for queue: 'oms.automation'> *<Caught exception adding value to cache fqn[/9976/root/0/Client_Details/1346158074198] value[null] nodeId[87386] nodeIndex[null]*
>
*org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/9976/root/0/Client_Details/1346158074198, caller=GlobalTransaction:<null>:887, lock=write*
*owner=GlobalTransaction:<null>:892 (org.jboss.cache.lock.LockStrategyReadCommitted@3fcbb918)*
Here's the situation:
We're using an oracle application that manages service orders life cycle. So we have specifics flows based at telecom industry business rules that access all time the same fqn.
In some flows we have integrations with others systems via webservices and jms queues who are responsible for allocating the equipment inventory. However, these integrations lasts 20 seconds on average.
Looking at the jboss cache configuration we observed that some parameters are not following the recommended configuration by the jboss specialists (please look at attached file omscache-config.xml ).
ps.: The parameter LockAcquisitionTimeout (30000 milliseconds) seems not to be sufficient.
Anyone have some ideas for the problem related?
ps2.: Sorry for the english :D
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/757029#757029]
Start a new discussion in JBoss Cache at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 8 months
[Beginner's Corner] - [org.apache.catalina.core.AprLifecycleL istener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /jboss/bin/native
by dhaval joshi
dhaval joshi [https://community.jboss.org/people/dhaval0129] created the discussion
"[org.apache.catalina.core.AprLifecycleL istener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /jboss/bin/native"
To view the discussion, visit: https://community.jboss.org/message/758142#758142
--------------------------------------------------------------
Hi,
I am using Jboss 4.2.3 , when I start jboss server ,It keeps gving me message as below,
2012-08-23 14:10:08,640 INFO -> (main)
[org.apache.catalina.core.AprLifecycleL istener] The Apache Tomcat
Native library which allows optimal performance in production
environments was not found on the java.library.path: /jboss/bin/native
I tried to configure tomcat apr and It still gives me another set of ssl error, below are the error
Can I configure tomcat APR in jboss ?, If yes How ?
Does configuring tomcat APR improves the JBoss performance ?
2012-09-05 13:32:29,741 INFO -> (main) [org.apache.catalina.core.AprLifecycleListener] APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
2012-09-05 13:32:29,852 ERROR -> (main) [org.apache.coyote.http11.Http11AprProtocol] Error initializing endpoint
java.lang.Exception: No Certificate file specified or invalid file format
at org.apache.tomcat.jni.SSLContext.setCertificate(Native Method)
at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:683)
at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:107)
at org.apache.catalina.connector.Connector.initialize(Connector.java:1073)
at org.apache.catalina.core.StandardService.initialize(StandardService.java:668)
at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:791)
at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
at org.apache.catalina.startup.Catalina.start(Catalina.java:568)
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.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.web.tomcat.service.JBossWeb.startService(JBossWeb.java:440)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInterceptor.java:124)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:109)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
2012-09-05 13:32:29,853 ERROR -> (main) [org.apache.catalina.startup.Catalina] Catalina.start
LifecycleException: Protocol handler initialization failed: java.lang.Exception: No Certificate file specified or invalid file format
at org.apache.catalina.connector.Connector.initialize(Connector.java:1075)
at org.apache.catalina.core.StandardService.initialize(StandardService.java:668)
at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:791)
at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
at org.apache.catalina.startup.Catalina.start(Catalina.java:568)
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.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.web.tomcat.service.JBossWeb.startService(JBossWeb.java:440)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInterceptor.java:124)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:109)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/758142#758142]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 8 months
[JBoss Web Services] - Re: My WebService Client always gets "Connection refused" Exception
by Matthias M.
Matthias M. [https://community.jboss.org/people/virtuellesnugat] created the discussion
"Re: My WebService Client always gets "Connection refused" Exception"
To view the discussion, visit: https://community.jboss.org/message/758061#758061
--------------------------------------------------------------
After I found out, thanks to wireshark, that the client tried to address localhost instead of the specified location, I knew what happened:
In the generated wsdl was the following part included:
{code:xml}
<wsdl:service name="AppointmentFacadeService">
<wsdl:port binding="tns:AppointmentFacadeServiceSoapBinding" name="AppointmentFacadePort">
<soap:address location=" http://localhost:8080/wsServe/AppointmentFacade http://localhost:8080/wsServe/AppointmentFacade"/>
</wsdl:port>
</wsdl:service>
{code:xml}
As my server is running on a vm, it's pretty obvious what caused the problem.
I was able to solve it by editing the standalone-full.xml
{code:xml}
<subsystem xmlns="urn:jboss:domain:webservices:1.1">
<modify-wsdl-address>true</modify-wsdl-address>
<wsdl-host>192.168.178.121</wsdl-host>
<endpoint-config name="Standard-Endpoint-Config"/>
<endpoint-config name="Recording-Endpoint-Config">
<pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
<handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>
</pre-handler-chain>
</endpoint-config>
</subsystem>
{code:xml}
This way, the above mentioned part of the wsdl was changed to this:
{code:xml}
<wsdl:service name="AppointmentFacadeService">
<wsdl:port binding="tns:AppointmentFacadeServiceSoapBinding" name="AppointmentFacadePort">
<soap:address location=" http://192.168.178.121:8080/wsServe/AppointmentFacade http://192.168.178.121:8080/wsServe/AppointmentFacade"/>
</wsdl:port>
</wsdl:service>
{code:xml}
And now my java se client addresses the correct service, though it picked the correct url to retrieve the wsdl.
I still got two questions left:
1. Why was SoapUI able to call the correct service? I know, I had to edit the interface endpoint by changing the url. But which method can I use to change it manually on client side in the java code?
2. It seems to be a very bad style to hardcode the machine's url into the configuration file in order to get the expected wsdl created. Is there a constant I can use like "{jboss-external-ipv4-address}"?
Best regards, Matthias
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/758061#758061]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 8 months
[JBoss Tools] - BrowserSim FAQ
by Yahor Radtsevich
Yahor Radtsevich [https://community.jboss.org/people/yradtsevich] modified the document:
"BrowserSim FAQ"
To view the document, visit: https://community.jboss.org/docs/DOC-18100
--------------------------------------------------------------
*Q: What is BrowserSim ?*
*A:* BrowserSim is a Browser Simulator which primarily is intended for having a quick, easy and multi-platform way of testing if your webapp will render and behave correctly on a mobile device.
*Q: How does BrowserSim works ?*
*A:* It wraps a webkit browser and makes it respond and send work like a mobile browser by spoofing content and media request headers.
*
Q: What do I need to run BrowserSim?*
*A:* The requirements for different platforms are as listed below:
* Windows:* Only 32-bit Eclipse/JBDS is supported;
* Apple http://www.apple.com/quicktime/download/ QuickTime or http://www.apple.com/itunes/download/ iTunes must be installed (they contain Apple Application Support which provides WebKit engine for BrowserSim).
* Linux:* WebKitGTK 1.2.0 or newer must be installed and available in the library load path.
* This should be available on RHEL and Ubuntu by default, if not use your package manager to install libwebkitgtk
* Mac OS X* It just works.
*Q: How to add BrowserSim to the toolbar?*
*A:* Go to Window → Customize Perspective and select "BrowserSim" under "Command Groups Availability". Then it becomes available in the global toolbar via the "phone" icon:
https://community.jboss.org/servlet/JiveServlet/showImage/102-18100-10-18... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18100-1...
*Q: Can I use the browser as a replacement for testing on a real phone or emulator?*
*A:* Browsersim make it easy to test basic layout questions/issues on any platform without having to install a platform specifc emulator or manually try use a phone.
That said it is not 100% reliable since there are so many different brands/versions of phones there will be differences in behavior, thus no, BrowserSim does not replace real or emulated phone testing.
For full verfication/testing you should test on a real phone.
*Q: BrowserSim shows an error message saying that JRE 7 is not supported on Windows and does not run (with JBoss Tools 3.4.0.Alpha1 and above).*
*A:* There is an incompatibility between some versions of JRE 7 and BrowserSim on Windows. To workaround this, please do the following:
1. Install JRE/JDK 6 or JDK 7 (but not JRE 7).
2. Add the next lines at the beginning of your eclipse.ini or jbdevstudio.ini:
-vm
PATH_TO_JAVA_INSTALLATION_DIRECTORY\bin\javaw.exe
*Q: BrowserSim shows the *"No more handles [Failed to load the swt-webkit library]"* error message and does not run (with JBoss Tools 3.3.0.GA and below).*
*A:* There is an incompatibility between some versions of JRE/JDK 7 and BrowserSim on Windows. To workaround this, please do the following:
1. Install JRE/JDK 6 (but not JRE/JDK 7).
2. Add the next lines at the beginning of your eclipse.ini or jbdevstudio.ini:
-vm
PATH_TO_JAVA_INSTALLATION_DIRECTORY\bin\javaw.exe
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-18100]
Create a new document in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
11 years, 8 months
