[JBoss Messaging] - Observing JMS Bridge Connections?
by julians37
I'm looking for a way to get notified by JBoss Messaging when a JMS Bridge to a remote broker goes down and comes up again. The connection between my bridged JMS brokers is not always available and I need to provide failover behaviour for when it is unavailable.
I've read the user documentation and I've taken a look at the code in Bridge.java, but it doesn't seem as if there would be any kind of notification mechanism in place. What would be the best way to implement this - would I have to provide a custom ConnectionFactory that creates wrapped connection objects handling the notification? Would it be better to use the aspect interface and advise the corresponding functions in javax.jms.Connection? Is there a more elegant way that I've overlooked?
In the long term, are there any plans to implement something akin to ApacheMQ's advisory messages?
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082436#4082436
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082436
18 years, 7 months
[JBossWS] - start JBoss problem
by leaderbird
I tried to follow jboss-5.0.0.Beta1 installation intructions to install jboss-5.0.0.Beta1on top of jboss-5.0.0.Beta1.
After that, I tried to start JBoss, but I saw a lot of exceptions, and http://localhost:8080/jbossws could not be reached. Am I missing anything in the steps? any comments are appreciated.
Part of the exception messages are
-------------------------------------------------------------------------
10:02:24,343 ERROR [BaseModelMBean] Exception invoking method addChild
org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser
at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100)
at org.jboss.web.metamodel.descriptor.WebDDObjectFactory.parse(WebDDObjectFactory.java:82)
at org.jboss.web.tomcat.tc6.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:256)
at org.jboss.web.tomcat.tc6.WebAppLoader.start(WebAppLoader.java:104)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4198)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5285)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.web.tomcat.tc6.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:302)
at org.jboss.web.tomcat.tc6.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:129)
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:355)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:88)
at org.jboss.web.deployers.WebModule.start(WebModule.java:66)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
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:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
at $Proxy0.start(Unknown Source)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
at org.jboss.system.ServiceController.start(ServiceController.java:431)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
at org.jboss.Main.boot(Main.java:210)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082435#4082435
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082435
18 years, 7 months
Re: Steps for Deploying the new EAR file (Hot Deployment ??)
by samk＠twinix.com
See Thread at: http://www.techienuggets.com/Detail?tx=11957 Posted on behalf of a User
bkucutc
In Response To:
Hi..,
What are the steps when you want to deploy the new war file to the server. Here are the steps I follow :
1. Shutdown the App server
2. Remove the EAR file from deploy folder
3. Go to the tmp folder & remove all the files related to the earlier app
4. Go to the work folder & remove all the files related to the earlier app
5. Deploy the new war file.
6. Start the app server.
Are these steps correct. ?
If I don't deploy the app as per the steps mentioned above, the App doesn't work fine & throws all kind of exceptions.
Our is a linux RH ES , HP bladed env.
Also , please let me know if there is any way to do the hot deployment on JBoss.
Regards,
Praveen
18 years, 7 months
[JBossCache] - Problems with NodeLocking algorithm
by jacek187
Problems with NodeLocking algorithm
Hi all
I?m fascinated with TreeCache and I think that this is a very good and powerful product. I?m trying to use it in my application where many concurrent puts/removes occurs ? and this is not easy task, because there are many unreasonable exceptions raised from TreeCache under heavy-load.
Because my application must work 24/7 without any unreasonable exceptions raised form any component I do some investigation and found, that node locking algorithm used by TreeCache (when using Pessimistic locking scheme) is not good enough.
Main ?work unit? in TreeCache is Node. Nodes have hierarchical structure like folders on disk. There is root node, root node has children, children have own children etc.
If operation needs modify data in node, lock must be acquired. Physically locks are a part of Node.
If we put data into /a/b/c/d node (on clear cache), first lock on / (root) node must be acquired. Then if / doesn?t contains a child, /a node must be created and lock must be acquired etc.
If all required nodes from path are locked with correct lock type (RL, WL), target operation can be invoked.
This is very simple and generally this works correctly in single-thread applications. But what happens when 2 threads are trying work on this same node?
Scenario 1:
There is /a node in cache.
Thread-0 is trying put new value into /a node, Thread-1 is trying remove /a node.
Both threads are in PessimistickLockInterceptor.lock() method, both treads have this same reference to /a node.
Thread-1 is acquiring WL lock on /a node and wins, Thread-0 is waiting for WL on /a node.
Now Thread-1 removes /a node from cache and until now / doesn?t contains /a node, but Thread-0 is still waiting for WL to /a node. Thread-1 commits transaction and release lock on /a node. Thread-0 acquired lock on /a. Because /a dosen?t exists in cache (was removed by Thread-1) this lock is invalid. This situation is handled by treecache properly, because he checks after lock acquisition if node still exists in cache
| do{
| lock(fqn, ctx.getGlobalTransaction(), lock_type, recursive, zeroLockTimeout ? 0 : lock_timeout, createIfNotExists, storeLockedNode, isRemoveData);
| }while (!cache.exists(fqn))
|
But what happens if between lock method and condition check another thread creates /a node?
Assume that Thread-0 is sleeping before loop condition check (this really happens in real-applications under heavy load). Thread-1 needs to put some data into previously removed /a node. Because / (root) dosen?t contains /a, new node /a is created, and WL on new node is acquired by Thread-1.
Now we have situation, when 2 threads have WL on this same node! This is possible, because lock table is located into node, and both threads have another instance of /a node.
Now Thread-1 is putting some data into /a node and commit operations, Thread-0 checks loop condition, and because /a node exists in cache, loop is released. Thread-0 is going into real _put operation. Now assume, that before invoke _put operation Thread-1 is removing again /a node. He can do this, because /a node from treecache hasn?t any information about WL lock (Thread-0 has WL, but in old node instance, different from instance form cache). Node /a is now removed from cache by Thread-1.
And now if Thread-0 try invoke _put operation, he can?t find /a node, findNode returns null
and NodeNotExistsException is raised.
This issue was observed and reported as bug http://jira.jboss.com/jira/browse/JBCACHE-1164
I think, that the simplest solution to this problem is to add additional condition to loop condition. Not only fqn exists condition should be checked, but node from cache with locked node should be compared. It?s easy to return locked node from lock() method and replace cache.exists with cache._get method and compare this 2 objects. If they are not this same object ? loop can be finished only if this objects are this same object. (or if result from lock method is null)
I have changed this code and it look works correctly now.
Scenario 2:
Cache is clear. Thread-0 is trying to remove /a node. He checks / (root) and because there is no any children, no WL lock was created. Because no lock has been created, no information to current transaction table about removed node is added. (Treecache in pessimistic locking scheme doesn?t is marking only nodes as removed when real _remove operation is invoked. Nodes are really removed in commit phase). Tread-0 is going into real _remove operation. Assume that Thread-0 sleeps before _remove execution (simulate heavy-load). Now Thread-1 is trying to put new data into /a/b/c/d node. He must checks whole path /a/b/c/d. because / (root) doesn?t contains any children, /a is created and then /a/b etc. Now Thread-1 needs to check end loop condition, but assume, that before this operation Thread-0 invokes _remove operation. Node /a is marked as removed, Thread-0 commit transaction etc. because transaction table doesn?t contains any information about removed nodes node was not real removed from cache. But this node is still marked as removed!
This is first problem in this scenario, this node is form now like ghost, because it still exists in cache, but is marked as removed.
This issue was observed and reported as bug http://jira.jboss.com/jira/browse/JBCACHE-1168
And we can see now next problem: Thread-1 needs to check end loop condition. Because exists method from cache default doesn?t returns nodes marked as removed, condition is true (!cache.exists), and again lock() method is called. Again / (root) is checked, but because getOrCreateChild doesn?t checks node for markAsRemoved condition, now Thread-1 looks, that / contains /a, /a contains /a/b etc. again WL on /a/b/c/d is acquired and again end loop condition is checked, again cache.exists returns false, again lock() is invoked etc. This loop never ends. Only chance to stop this is TimeoutException, but because Thread-1 has already owned all locks, there is no chance to TimeoutException to be thrown.
This issue (endless loop) was observed and reported as bug http://jira.jboss.com/jira/browse/JBCACHE-1165
I think, that because real _remove operation is always invoked (both when node is locked and when node doesn?t exists and no lock is acquired), the simplest solution is to set flag createIfNotExists=true on removeNodeMethod. I have added this condition and it look works correctly.
To break infinitive loop (in another, yet unknown cases), I think that max time to spent in this loop can?t be greater than lock acquisition timeout, so in loop check condition should be added.
Scenario 3:
Cache is clear. Similar to scenario 2 but with small, but important difference. First starts Thread-1. Thread-1 is putting new data into /a/b/c/d. Because WL is acquired only on target node, on nodes /a /a/b and /a/b/c only RL is acquired. Assume, that Thread-1has acquired RL on /a/b/c. Assume that Thread-1 sleep for some time now (simulate heavy-load). Now Thread-0 starts and is trying to remove /a node. Thread-0 needs lock with WL /a and /a children?s. Thread-0 locks /a, /a/b, and /a/b/c with WL (he can do this, because Thread-1 has only RL) and because now /a/b/c node doesn?t contains any children (Thread-1 is sleeping). Thread-0 checks end loop condition and is going into real _remove operation. Now assume that Thread-0 is going to sleep and Thread-1 wakes up. Thread-1 create /a/b/c/d node and acquire WL on this node, and is going into real _put operation. Now if Thread-0 removes node /a/b/c/d before Thread-1 finds node /a/b/c/d, Thread-1 will throw NodeNotExistsException from _put operation, because for Thread-1 this node is locked but couldn?t be found in cache.
I don?t known how this situation could be the best handled. The simplest solution is to acquire WL on node instead RL when node is created, but I have not yet tested this solution.
I hope, that this information helps TreeCache team to solve problems with parallel work to fast as its possible, because now it?s impossible to use Treecache (in PessimistickLock mode) in multithread applications, where many concurrent put/remove operations from this same regions occurs.
Jacek Halat
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082429#4082429
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082429
18 years, 7 months
[Installation, Configuration & DEPLOYMENT] - cant start jboss AS 5 clean from europa eclipse
by wiggy
having a problem starting jboss AS 5 beta 2 from eclipse.
i unpacked the eclipse build and tried to create new server config for version 5 and get the following when i run it
did this by windoows/properties/server/installed server environements - then add new and select jboss v5 as the AS .
this is the error log.
| 22:58:40,933 INFO [ServerImpl] Starting JBoss (Microcontainer)...
| 22:58:40,953 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta2 (build: SVNTag=JBoss_5_0_0_Beta2 date=200704060017)
| 22:58:40,953 INFO [ServerImpl] Home Dir: E:\jboss\jboss-5.0.0.Beta2
| 22:58:40,953 INFO [ServerImpl] Home URL: file:/E:/jboss/jboss-5.0.0.Beta2/
| 22:58:40,953 INFO [ServerImpl] Library URL: file:/E:/jboss/jboss-5.0.0.Beta2/lib/
| 22:58:40,963 INFO [ServerImpl] Patch URL: null
| 22:58:40,963 INFO [ServerImpl] Server Name: default
| 22:58:40,963 INFO [ServerImpl] Server Home Dir: E:\jboss\jboss-5.0.0.Beta2\server\default
| 22:58:40,963 INFO [ServerImpl] Server Home URL: file:/E:/jboss/jboss-5.0.0.Beta2/server/default/
| 22:58:40,993 INFO [ServerImpl] Server Data Dir: E:\jboss\jboss-5.0.0.Beta2\server\default\data
| 22:58:40,993 INFO [ServerImpl] Server Temp Dir: E:\jboss\jboss-5.0.0.Beta2\server\default\tmp
| 22:58:40,993 INFO [ServerImpl] Server Config URL: file:/E:/jboss/jboss-5.0.0.Beta2/server/default/conf/
| 22:58:40,993 INFO [ServerImpl] Server Library URL: file:/E:/jboss/jboss-5.0.0.Beta2/server/default/lib/
| 22:58:40,993 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
| 22:58:41,394 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/E:/jboss/jboss-5.0.0.Beta2/server/default/conf/bootstrap-beans.xml
| 22:58:45,820 INFO [ProfileImpl] Using profile root:E:\jboss\jboss-5.0.0.Beta2\server\default
| 22:58:48,163 ERROR [AbstractKernelController] Error installing to Instantiated: name=DeploymentFilter state=Described
| java.lang.IllegalStateException: Class not found: [Ljava.lang.String;
| at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:174)
| at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:125)
| at org.jboss.metadata.spi.signature.Signature.getParametersTypes(Signature.java:292)
| at org.jboss.metadata.plugins.loader.reflection.AnnotatedElementMetaDataLoader.getComponentMetaDataRetrieval(AnnotatedElementMetaDataLoader.java:138)
| at org.jboss.metadata.plugins.context.AbstractMetaDataContext.getComponentMetaDataRetrieval(AbstractMetaDataContext.java:280)
| at org.jboss.metadata.spi.retrieval.MetaDataRetrievalToMetaDataBridge.getComponentMetaData(MetaDataRetrievalToMetaDataBridge.java:159)
| at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.methodHasAnnotations(AOPConstructorJoinpoint.java:202)
| at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasMethodMetaData(AOPConstructorJoinpoint.java:172)
| at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasInstanceOrJoinpointMetaData(AOPConstructorJoinpoint.java:152)
| at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:99)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103)
| at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:52)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:302)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119)
| at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:64)
| at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:76)
| at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:146)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.deploy(ProfileServiceBootstrap.java:295)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:222)
| at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
| at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
| at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
| at org.jboss.Main.boot(Main.java:210)
| at org.jboss.Main$1.run(Main.java:522)
| at java.lang.Thread.run(Unknown Source)
| Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String;
| at java.net.URLClassLoader$1.run(Unknown Source)
| at java.security.AccessController.doPrivileged(Native Method)
| at java.net.URLClassLoader.findClass(Unknown Source)
| at java.lang.ClassLoader.loadClass(Unknown Source)
| at java.lang.ClassLoader.loadClass(Unknown Source)
| at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:170)
| ... 35 more
| 22:58:49,165 INFO [ServerInfo] Java version: 1.6.0_02,Sun Microsystems Inc.
| 22:58:49,165 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0_02-b06,Sun Microsystems Inc.
| 22:58:49,165 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
| 22:58:49,375 INFO [JMXKernel] Legacy JMX core initialized
| Failed to boot JBoss:
| java.lang.RuntimeException: Exception during Bootstrap
| at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:99)
| at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
| at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
| at org.jboss.Main.boot(Main.java:210)
| at org.jboss.Main$1.run(Main.java:522)
| at java.lang.Thread.run(Unknown Source)
| Caused by: org.jboss.deployers.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
|
| VFSBootstrapScanner
| -> DeploymentFilter{Configured:**ERROR**}
|
| VFSDeployerScanner
| -> DeploymentFilter{Configured:**ERROR**}
|
| VFSDeploymentScanner
| -> DeploymentFilter{Configured:**ERROR**}
|
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| DeploymentFilter -> java.lang.ClassNotFoundException: [Ljava.lang.String;
|
|
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.checkIncomplete(ProfileServiceBootstrap.java:389)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:236)
| at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
| ... 5 more
|
anyone else had any luck getting the europa build to start jboss 5.
works fine with a server config for 4.2 though.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082427#4082427
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082427
18 years, 7 months
[JBossWS] - Re: Accessing a Java JBossWS WebService from VBScript not wo
by gbc＠gmx.de
Uh,
Trying MSSoapToolkit 3.0 made it even worse... Now, if calling method hello from this class:
| @Stateless
| @WebService
| @WebContext(contextRoot="/SimpleWebServices")
| @SOAPBinding(style = SOAPBinding.Style.RPC)
| public class SimpleWeb implements SimpleWebInterface {
|
| @WebMethod
| public boolean isAlive() {
| System.out.println("SimpleWeb.isAlive()");
| return true;
| }
|
| @WebMethod
| public String hello(@WebParam(name="name") String name) {
| System.out.println("SimpleWeb.helloWorld(): " + name);
| return "Hello " + name + "!";
| }
|
| }
|
with this vbscript:
| Option Explicit
|
| Dim wsdl, c, r
|
| wsdl = "http://localhost:8080/SimpleWebServices/SimpleWeb?wsdl"
|
| set c = CreateObject("MSSOAP.SoapClient30")
| c.mssoapinit(wsdl)
|
| set r = c.hello("World")
|
| WScript.Echo r
|
I get:
| C:\Data\Tests>cscript SimpleWebService.vbs
| Microsoft (R) Windows Script Host Version 5.6
| Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
|
| C:\Data\Tests\SimpleWebService.vbs(10, 1) (null): Cannot find child element: name
|
With following log entries in Jboss 4.2.0 GA with JBossWS 1.2.1 GA and Seam 2.0 Beta 1:
| 2007-09-09 23:11:10,921 TRACE [org.jboss.ws.core.MessageTrace] Incoming Request Message
| <SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' xmlns:SOAPSDK1='http://www.w3.org/2001/XMLSchema' xmlns:SOAPSDK2='http://www.w3.org/2001/XMLSchema-instance' xmlns:SOAPSDK3='http://schemas.xmlsoap.org/soap/encoding/'>
| <SOAP-ENV:Header/>
| <SOAP-ENV:Body>
| <SOAPSDK4:hello xmlns:SOAPSDK4='http://webservice.simple/'>
| <SOAPSDK4:name xmlns:SOAPSDK4='http://webservice.simple/'>World</SOAPSDK4:name>
| </SOAPSDK4:hello>
| </SOAP-ENV:Body>
| </SOAP-ENV:Envelope>
| 2007-09-09 23:11:10,921 TRACE [org.jboss.ws.core.CommonMessageContext] put: APPLICATION:javax.xml.ws.binding.attachments.inbound={}
| 2007-09-09 23:11:10,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: POST
| 2007-09-09 23:11:10,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: PRE
| 2007-09-09 23:11:10,937 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] addHandler:
| HandlerMetaDataJAXWS:
| type=PRE
| name=SOAP Request Handler
| class=class org.jboss.seam.webservice.SOAPRequestHandler
| params=[]
| protocols=##SOAP11_HTTP
| services=null
| ports=null
| 2007-09-09 23:11:10,937 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: ENDPOINT
| 2007-09-09 23:11:10,937 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: POST
| 2007-09-09 23:11:10,937 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=POST,info=[service={http://webservice.simple/}SimpleWebService,port=...]
| 2007-09-09 23:11:10,937 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
| 2007-09-09 23:11:10,937 TRACE [org.jboss.ws.core.CommonMessageContext] get(javax.xml.ws.handler.message.outbound): APPLICATION:javax.xml.ws.handler.message.outbound=false
| 2007-09-09 23:11:10,953 TRACE [org.jboss.ws.core.CommonMessageContext] get(javax.xml.ws.addressing.context.inbound): null
| 2007-09-09 23:11:10,953 DEBUG [org.jboss.ws.core.soap.SOAPMessageDispatcher] getDispatchDestination: {http://webservice.simple/}hello
| 2007-09-09 23:11:10,953 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] unbindRequestMessage: {http://webservice.simple/}hello
| 2007-09-09 23:11:10,953 DEBUG [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] Begin response processing
| 2007-09-09 23:11:10,953 TRACE [org.jboss.ws.core.CommonMessageContext] get(javax.xml.ws.handler.message.outbound): APPLICATION:javax.xml.ws.handler.message.outbound=false
| 2007-09-09 23:11:10,953 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@a877c0 (Thread http-0.0.0.0-8080-1)
| 2007-09-09 23:11:10,953 TRACE [org.jboss.ws.core.CommonMessageContext] put: APPLICATION:javax.xml.ws.handler.message.outbound=true
| 2007-09-09 23:11:10,953 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@1ceb670 (Thread http-0.0.0.0-8080-1)
| 2007-09-09 23:11:10,968 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception
| org.jboss.ws.WSException: Cannot find child element: name
| at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:866)
| at org.jboss.ws.core.CommonSOAPBinding.unbindRequestMessage(CommonSOAPBinding.java:325)
| at org.jboss.ws.core.server.AbstractServiceEndpointInvoker.invoke(AbstractServiceEndpointInvoker.java:187)
| at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:212)
| at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448)
| at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
| at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:595)
|
with Outgoing message:
| 2007-09-09 23:11:11,125 TRACE [org.jboss.ws.core.MessageTrace] Outgoing Response Message
| <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
| <env:Header/>
| <env:Body>
| <env:Fault xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
| <faultcode>env:Server</faultcode>
| <faultstring>Cannot find child element: name</faultstring>
| </env:Fault>
| </env:Body>
| </env:Envelope>
|
Don't know what else to do... At least, the soap fault is transerred and interpreted by vbscript corrctly ;-)
I tried to remove the Annotation:
| @SOAPBinding(style = SOAPBinding.Style.RPC)
|
but then any parameters for the method gave me null result at server with no error thrown, so vbs is not able to post correct value. Even stranger: calling the simple isAlive Method from above gave me errors of an incorrect numbers of parameters. How can no paramters != no parameters when just used: call c.isAlive()
What's next. I have no clue... Micros*ft says, Soapkit is deprecated and one should use dotnet to call webservices. but i found no example for vbsscript how to do that. .Net framework 2.0 is already installed, but how to call from vbscript? And with or without RPC styled SoapBinding on ServerSide?
Thank you for your time and help,
Greetz GHad
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082425#4082425
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082425
18 years, 7 months
