[Design of JBoss Remoting, Unified Invokers] - Problem in jboss integration with minimal deployment integra
by nithyaraj
Hi,
I have problem in integration of minimal deployement with webservice integration.can u give solution for this?
---------------
C:\Documents and Settings\nithyaraj>run -c minimal
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: E:\myjboss\jboss-4.2.2.GA
JAVA: E:\JDK1.5\jdk1.5.0_08\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli
ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: E:\JDK1.5\jdk1.5.0_08\lib\tools.jar;E:\myjboss\jboss-4.2.2.GA\bin\r
un.jar
===============================================================================
17:20:45,406 INFO [Server] Starting JBoss (MX MicroKernel)...
17:20:45,406 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=
JBoss_4_2_2_GA date=200710221139)
17:20:45,406 INFO [Server] Home Dir: E:\myjboss\jboss-4.2.2.GA
17:20:45,406 INFO [Server] Home URL: file:/E:/myjboss/jboss-4.2.2.GA/
17:20:45,406 INFO [Server] Patch URL: null
17:20:45,406 INFO [Server] Server Name: minimal
17:20:45,406 INFO [Server] Server Home Dir: E:\myjboss\jboss-4.2.2.GA\server\mi
nimal
17:20:45,406 INFO [Server] Server Home URL: file:/E:/myjboss/jboss-4.2.2.GA/ser
ver/minimal/
17:20:45,406 INFO [Server] Server Log Dir: E:\myjboss\jboss-4.2.2.GA\server\min
imal\log
17:20:45,406 INFO [Server] Server Temp Dir: E:\myjboss\jboss-4.2.2.GA\server\mi
nimal\tmp
17:20:45,406 INFO [Server] Root Deployment Filename: jboss-service.xml
17:20:45,968 INFO [ServerInfo] Java version: 1.5.0_08,Sun Microsystems Inc.
17:20:45,968 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_08-b03
,Sun Microsystems Inc.
17:20:45,968 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
17:20:47,125 INFO [Server] Core system initialized
17:20:51,250 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:jboss-log4j.xml
17:20:53,312 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
version) - JBoss Inc.
17:20:53,312 INFO [TransactionManagerService] Setting up property manager MBean
and JMX layer
17:20:53,687 INFO [TransactionManagerService] Starting recovery manager
17:20:53,843 INFO [TransactionManagerService] Recovery manager started
17:20:53,843 INFO [TransactionManagerService] Binding TransactionManager JNDI R
eference
17:20:59,421 INFO [STDOUT] no object for null
17:20:59,421 INFO [STDOUT] no object for null
17:20:59,453 INFO [STDOUT] no object for null
17:20:59,500 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
17:20:59,546 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
17:21:02,218 INFO [NativeServerConfig] JBoss Web Services - Native
17:21:02,218 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=20071021
0837)
17:21:03,687 INFO [Embedded] Catalina naming disabled
17:21:04,015 INFO [AprLifecycleListener] The Apache Tomcat Native library which
allows optimal performance in production environments was not found on the java
.library.path: E:\JDK1.5\jdk1.5.0_08\bin;.;C:\WINNT\system32;C:\WINNT;C:\WINNT\s
ystem32;C:\WINNT;C:\WINNT\System32\Wbem;E:\JDK1.5\jdk1.5.0_08\bin;E:\myjboss\jbo
ss-4.2.2.GA\bin;E:\apache-ant-1.7.0\bin;
17:21:04,187 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0
.1-8080
17:21:04,203 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80
09
17:21:04,203 INFO [Catalina] Initialization processed in 520 ms
17:21:04,203 INFO [StandardService] Starting service jboss.web
17:21:04,218 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
17:21:04,359 INFO [Catalina] Server startup in 148 ms
17:21:04,578 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w
eb.deployer/ROOT.war/
17:21:06,703 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
http-invoker.sar/invoker.war/
17:21:07,921 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/
jbossws.sar/jbossws-context.war/
17:21:08,390 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-local-jdbc.rar
17:21:09,593 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
17:21:09,656 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.ejb3:service=EJB3Deployer
State: CONFIGURED
I Depend On:
jboss.aop:service=AspectDeployer
jboss.ejb:service=EJBDeployer
jboss.ejb3:service=JarsIgnoredForScanning
Depends On Me:
jboss.ws:service=DeployerInterceptorEJB3
ObjectName: jboss.ws:service=DeployerInterceptorEJB21
State: CONFIGURED
I Depend On:
jboss.ejb:service=EJBDeployer
ObjectName: jboss.ws:service=DeployerInterceptorEJB3
State: CONFIGURED
I Depend On:
jboss.ejb3:service=EJB3Deployer
ObjectName: jboss.jdbc:service=metadata,datasource=DefaultDS
State: CONFIGURED
I Depend On:
jboss.jdbc:service=metadata
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.ejb:service=EJBDeployer
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb3:service=EJB3Deployer
jboss.ws:service=DeployerInterceptorEJB21
ObjectName: jboss.jdbc:service=metadata
State: NOTYETINSTALLED
Depends On Me:
jboss.jdbc:service=metadata,datasource=DefaultDS
17:21:09,968 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
080
17:21:10,000 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
17:21:10,015 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBos
s_4_2_2_GA date=200710221139)] Started in 24s:609ms
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125492#4125492
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125492
16 years, 3 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Unique Post Office Id
by timfox
"dimitris(a)jboss.org" wrote : Can't find the discussion thread, sorry.
|
| Again, my point is why not printing a warning and choosing a temporary id?
|
|
Well if it was that simple, we'd have probably done it already?
The problem is that the id is used to identify the nodes permanent storage - so it cannot be transient, it has to persist between restarts.
Also it's an integer, and we'd have to make sure it's unique across all nodes in the cluster.
Doing that automatically is non trivial - you need some kind of HA singleton counter that dishes out IDs (yuck).
Alternatives would be to make it a GUID, but it's used as a key in the message data tables so this would have performance implications.
Also making it a GUID would probably p*off some sys admins since an integer id makes it easy to identify a particular server (server 1, server 2, server 3 etc), whereas a GUID does not.
As Aaron pointed out, passing in a sys prop is a good idea.
Brian Stansberry also suggested we should have some kind of concept of server id at the AS level - then we could just use that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125477#4125477
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125477
16 years, 3 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Unique Post Office Id
by dimitris＠jboss.org
Can't find the discussion thread, sorry.
Again, my point is why not printing a warning and choosing a temporary id?
Sure, it may not make perfect sense (as with other services in jboss) that need proper configuration, but it'll let the server gracefully complete the booting sequence.
At this point the Post Office is the only service that complains when trying to create an instant cluster by forking the all configuration, either for demo or testing purposes:
| 13:11:33,796 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of
| incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual Stat
| e}
|
| jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory
| -> jboss.messaging:service=PostOffice{Start:**ERROR**}
| -> jboss.messaging:service=PostOffice{Create:**ERROR**}
|
| jboss.messaging.connectionfactory:service=ClusteredConnectionFactory
| -> jboss.messaging:service=PostOffice{Start:**ERROR**}
| -> jboss.messaging:service=PostOffice{Create:**ERROR**}
|
| jboss.messaging.connectionfactory:service=ConnectionFactory
| -> jboss.messaging:service=PostOffice{Start:**ERROR**}
| -> jboss.messaging:service=PostOffice{Create:**ERROR**}
|
| jboss.messaging.destination:name=DLQ,service=Queue
| -> jboss.messaging:service=PostOffice{Create:**ERROR**}
| -> jboss.messaging:service=PostOffice{Start:**ERROR**}
|
| jboss.messaging.destination:name=ExpiryQueue,service=Queue
| -> jboss.messaging:service=PostOffice{Create:**ERROR**}
| -> jboss.messaging:service=PostOffice{Start:**ERROR**}
|
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| jboss.messaging:service=PostOffice -> java.lang.IllegalArgumentException: Cannot
| start post office since there is already a post office in the cluster with the
| same node id (0). Are you sure you have given each node a unique node id during
| installation?
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125474#4125474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125474
16 years, 3 months
[Design of JBoss Web Services] - Re: [Productivity] Level 2 - Development
by alessio.soldano＠jboss.com
"alessio.soldano(a)jboss.com" wrote :
| Speaking of samples, we think to provide meaningful advanced samples. These might cover the testcases I spoke about in the productivity introduction http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095128#4094685, supporting tutorials in the documentation on advanced topics like security, attachments, addressing, etc.
Just to keep this thread online, I'm working on the advanced samples. Up to know there're 2 scenarios I'll soon describe in the wiki:
- the first one is about ws technologies related to attachments and security+authentication: this means MTOM/XOP, SWA, WS-Security, use of HTTPS, BASIC authentication. Different implementations are showed and the advantages and disadvantages coming from them will be discussed in the documentation
- the second one is about technologies providing means of performing asynchronous ws invocations: this means the JAX-WS API (using Future<?>, Response<?> ...), WS-Addressing, JMS endpoints (still need to implement this in the sample). As for the previous scenario, several implementation are provided and will be discussed in the documentation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125409#4125409
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125409
16 years, 3 months