[Installation, Configuration & Deployment] - Re: ERROR [AjpMessage] Invalid message recieved with signatu
by john_es
Ah, OK... just didn't want to post a huge thing if it wasn't necessary... or if I miss an obvious this in this output.
Here it is. Let me know if there's anything else I can post.
| =========================================================================
|
| JBoss Bootstrap Environment
|
| JBOSS_HOME: /opt/jboss
|
| JAVA: java
|
| JAVA_OPTS: -Dprogram.name=run.sh -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
|
| CLASSPATH: /opt/jboss/bin/run.jar
|
| =========================================================================
|
| 10:58:13,130 INFO [Server] Starting JBoss (MX MicroKernel)...
| 10:58:13,134 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)
| 10:58:13,137 INFO [Server] Home Dir: /opt/jboss
| 10:58:13,137 INFO [Server] Home URL: file:/opt/jboss/
| 10:58:13,138 INFO [Server] Patch URL: null
| 10:58:13,138 INFO [Server] Server Name: myproj
| 10:58:13,138 INFO [Server] Server Home Dir: /opt/jboss/server/myproj
| 10:58:13,138 INFO [Server] Server Home URL: file:/opt/jboss/server/myproj/
| 10:58:13,139 INFO [Server] Server Log Dir: /opt/jboss/server/myproj/log
| 10:58:13,139 INFO [Server] Server Temp Dir: /opt/jboss/server/myproj/tmp
| 10:58:13,139 INFO [Server] Root Deployment Filename: jboss-service.xml
| 10:58:14,014 INFO [ServerInfo] Java version: 1.6.0_0,Sun Microsystems Inc.
| 10:58:14,014 INFO [ServerInfo] Java VM: OpenJDK Client VM 14.0-b16,Sun Microsystems Inc.
| 10:58:14,014 INFO [ServerInfo] OS-System: Linux 2.6.31-14-generic,i386
| 10:58:14,744 INFO [Server] Core system initialized
| 10:58:18,402 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
| 10:58:18,404 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
| 10:58:19,148 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
| 10:58:19,148 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
| 10:58:19,321 INFO [TransactionManagerService] Starting recovery manager
| 10:58:19,420 INFO [TransactionManagerService] Recovery manager started
| 10:58:19,420 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
| 10:58:22,313 INFO [EJB3Deployer] Starting java:comp multiplexer
| 10:58:25,557 INFO [NativeServerConfig] JBoss Web Services - Native
| 10:58:25,557 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
| 10:58:28,104 INFO [Embedded] Catalina naming disabled
| 10:58:28,301 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/jni:/lib:/usr/lib
| 10:58:28,348 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
| 10:58:28,348 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
| 10:58:28,348 INFO [Catalina] Initialization processed in 244 ms
| 10:58:28,349 INFO [StandardService] Starting service jboss.web
| 10:58:28,350 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
| 10:58:28,387 INFO [Catalina] Server startup in 38 ms
| 10:58:28,595 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
| 10:58:30,359 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
| 10:58:31,053 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
| 10:58:31,437 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
| 10:58:32,320 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
| 10:58:33,463 INFO [MailService] Mail Service bound to java:/Mail
| 10:58:33,600 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
| 10:58:33,623 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
| 10:58:33,638 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
| 10:58:33,657 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
| 10:58:33,728 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
| 10:58:33,745 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
| 10:58:33,767 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
| 10:58:33,773 INFO [QuartzResourceAdapter] start quartz!!!
| 10:58:33,904 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
| 10:58:33,928 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
| 10:58:33,932 INFO [RAMJobStore] RAMJobStore initialized.
| 10:58:33,932 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
| 10:58:33,932 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
| 10:58:33,932 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
| 10:58:36,076 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
| 10:58:36,362 INFO [A] Bound to JNDI name: queue/A
| 10:58:36,363 INFO [B] Bound to JNDI name: queue/B
| 10:58:36,364 INFO [C] Bound to JNDI name: queue/C
| 10:58:36,366 INFO [D] Bound to JNDI name: queue/D
| 10:58:36,368 INFO [ex] Bound to JNDI name: queue/ex
| 10:58:36,388 INFO [testTopic] Bound to JNDI name: topic/testTopic
| 10:58:36,389 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
| 10:58:36,390 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
| 10:58:36,392 INFO [testQueue] Bound to JNDI name: queue/testQueue
| 10:58:36,433 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
| 10:58:36,483 INFO [DLQ] Bound to JNDI name: queue/DLQ
| 10:58:36,571 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
| 10:58:36,602 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=mysql-myproj' to JNDI name 'java:mysql-myproj'
| 10:58:36,798 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
| 10:58:37,004 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
| 10:58:37,036 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
| 10:58:37,045 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 23s:904ms
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263681#4263681
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263681
16 years, 5 months
[jBPM Users] - jBPM 4.x : roadmap BAR/PAR format
by dtoch
I'm evaluating jBPM 4.1. Currently if you take for example a simple PDF file and rename the extension to BAR/PAR to indicate it's a process archive, it will get deployed without any warnings or errors!
The solution we envisage to avoid this problem is by imposing the presence of a file JBPM_LISTING in the BAR/PAR:
MyProcesses.bar/
META-INF/
JBPM_LISTING
myprocesses/
Process.jpdl.xml
Subprocess.jpdl.xml
InformationVO.class
Translations.properties
with JBPM_LISTING:
myprocesses/Process.jpdl.xml
myprocesses/Subprocess.jpdl.xml
myprocesses/InformationVO.class
myprocesses/Translations.properties
During pre-deployment, if JBPM_LISTING contains an entry for a file that doesn't exist in the PAR/BAR then it would throw a validation error. Similar behaviour if files are discovered in the PAR/BAR which aren't defined in JBM_LISTING.
Q : would it be interesting to include this kind of feature in the JBPM roadmap?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263674#4263674
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263674
16 years, 5 months