2015-01-23 2 views
-1

나는 다음과 같은 구성으로 새로운 IBM Mobilefirst 재단 플랫폼 6.3을 구축하고를 배포 한 후 응답하지 3. DB - MySQL 5.6.22 4. OS - RHEL 6.5IBM Mobilefirst 재단 플랫폼 6.3 Tomcat은 런타임

그것은 MobileFirst Console까지 계속 작동합니다. 서버 구성 도구를 사용하여 런타임을 배포 한 후 중지 명령을 포함하여 Tomcat이 응답을 중지합니다. 나는 그것을 수동으로 죽여야 만한다. 런타임을 배포 취소하면 Tomcat이 올바르게 작동합니다. war 파일은 studio v6.3을 사용하여 만든 간단한 Hello MobileFirst 프로젝트입니다.

동일한 호스트에서 WAS Liberty Core 8.5.5.4를 사용하여 동일하게 리빌드합니다. 정상적으로 작동합니다. 나는 JMX와 관련이 있다고 추측하고있다. 포트가 차단되어있을 수있다. 나는 jconsole을 tomcat 인스턴스에 연결하려고 시도했다. 연결되어 있고 나는 모니터링 차트를 볼 수있다.

아이디어가 있으십니까? 그것은 톰캣에서 서버의 JMX 구성이 올바른지 아니라고 할 수있다

Jan 14, 2015 4:19:02 PM com.worklight.server.database.api.WorklightDataSource createResourceRefDatasource 
FINE: Entering, resourceRefName=jdbc/WorklightDS [project devworklight] 
Jan 14, 2015 4:19:02 PM com.worklight.server.database.api.WorklightDataSource extractDbTypeFromURL 
FINE: Entering: url = jdbc:mysql://137.57.137.41:3306/WRKLGHT [project devworklight] 
Jan 14, 2015 4:19:02 PM com.worklight.server.database.api.WorklightDataSource extractDbTypeFromURL 
FINE: Driver class name = com.mysql.jdbc.Driver [project devworklight] 
Jan 14, 2015 4:19:02 PM com.worklight.server.database.api.WorklightDataSource extractDbTypeFromURL 
FINE: Extracted DB type = MYSQL [project devworklight] 
Jan 14, 2015 4:19:02 PM com.worklight.server.database.api.WorklightDataSource afterPropertiesSet 
INFO: FWLSE0192I: JNDI resource jdbc/WorklightDS is mapped to MYSQL DB type [project devworklight] 
Jan 14, 2015 4:19:02 PM com.worklight.server.database.api.WorklightDataSource afterPropertiesSet 
FINE: Discovered DB type =MYSQL [project devworklight] 
Jan 14, 2015 4:19:02 PM org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean createNativeEntityManagerFactory 
INFO: Building JPA container EntityManagerFactory for persistence unit 'WorklightPU' 
15 WorklightPU WARN [localhost-startStop-1] openjpa.Runtime - An error occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root URL [file:/var/tomcat/wle1/Worklight/devworklight/worklight-jee-library.jar]. The error has been consumed. To see it, set your openjpa.Runtime log level to TRACE. Load-time class transformation will not be available. 
Jan 14, 2015 4:19:02 PM com.worklight.analytics.AnalyticsHttpServiceImpl getServerProperties 
FINE: Analytics is disabled; data will not be forwarded to IWAP because wl.analytics.url property is not set. 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.JNDIUtils globalScopeLookup 
FINE: JNDI Access via globalScopeLookup to ibm.worklight.topology.platform => Tomcat 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.JNDIUtils applicationScopeLookup 
WARNING: Access to JNDI property ibm.worklight.topology.clustermode with null context path 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.JNDIUtils applicationScopeLookup 
FINE: JNDI Access via applicationScopeLookup in null to ibm.worklight.topology.clustermode => Standalone 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.jmx.MBeanConnectorFactory getRuntimeMBeanHandler 
FINE: found Tomcat runtime 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.GeneralUtil scanAllIPv4Interfaces 
FINE: found IP address:/fe80:0:0:0:250:56ff:feaf:169%2 [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.GeneralUtil scanAllIPv4Interfaces 
FINE: found IP address:/137.57.137.10 [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.core.auth.impl.AuthenticationContext AuthenticationContext 
FINE: Create authentication context [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.BaseProjectLocal set 
FINE: Set ProjectLocal: devworklight 
java.lang.Exception: Stack trace 
    at java.lang.Thread.dumpStack(Thread.java:1365) 
    at com.worklight.common.util.BaseProjectLocal.set(BaseProjectLocal.java:54) 
    at com.worklight.core.tasks.TaskThread.run(TaskThread.java:95) 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.BaseProjectLocal set 
FINE: Set ProjectLocal returned: true [project devworklight] 
541 WorklightPU INFO [localhost-startStop-1] openjpa.Runtime - Starting OpenJPA 1.2.2 
569 WorklightPU INFO [localhost-startStop-1] openjpa.jdbc.JDBC - Using dictionary class "com.worklight.database.WorklightMySQLDBDictionary". 
Jan 14, 2015 4:19:03 PM com.worklight.server.database.api.WorklightDataSource afterPropertiesSet 
INFO: FWLSE0187I: jdbc/WorklightReportsDS data source is disabled. No connection opened. [project devworklight] 
Jan 14, 2015 4:19:03 PM org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean createNativeEntityManagerFactory 
INFO: Building JPA container EntityManagerFactory for persistence unit 'WorklightReportsPU' 
1 WorklightReportsPU WARN [localhost-startStop-1] openjpa.Runtime - An error occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightReportsPU', root URL [file:/var/tomcat/wle1/Worklight/devworklight/worklight-jee-library.jar]. The error has been consumed. To see it, set your openjpa.Runtime log level to TRACE. Load-time class transformation will not be available. 
Jan 14, 2015 4:19:03 PM com.worklight.report.impl.GadgetReportsServiceImpl loadProperties 
INFO: FWLSE0186I: Application raw reports are disabled. [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.report.impl.AnalyticsServiceImpl loadProperties 
FINE: AnalyticsServiceImpl.loadProperties [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.mgmt.impl.ApplicationManagementImpl ProjectManagementMXBeanImpl 
FINE: ProjectManagementMXBeanImpl [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.core.jmx.ProjectManagementMXBeanImpl ProjectManagementMXBeanImpl 
FINE: ProjectManagementMXBeanImpl [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.JNDIUtils applicationScopeLookup 
FINE: JNDI Access via applicationScopeLookup in devworklight to ibm.worklight.admin.environmentid => Dev_Worklight 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.JNDIFromPropertiesUtil getPropertiesFromFile 
WARNING: File not found. Context path is __globalscope__ 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.JNDIUtils globalScopeLookup 
FINE: JNDI Access via globalScopeLookup to ibm.worklight.admin.serverid => null 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.jmx.LibertyJMXRegister register 
FINE: detected single server mode. [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.jmx.LibertyJMXRegister register 
INFO: FWLSE2008I: MBean registration succeeded for: com.worklight.common.server.jmx.api:type=ProjectManagement_Dev_Worklight,qualifier=devworklight [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.server.bundle.project.JeeProjectActivator contextInitialized 
FINE: Start JMX initialization [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.core.auth.impl.AuthenticationFilter setSyncRequired 
INFO: FWLSE0273I: Set sync required to 'true' [project devworklight] 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.JNDIUtils applicationScopeLookup 
FINE: JNDI Access via applicationScopeLookup in devworklight to ibm.worklight.admin.environmentid => Dev_Worklight 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.jmx.MBeanConnectorFactory getRuntimeMBeanHandler 
FINE: found Tomcat runtime 
Jan 14, 2015 4:19:03 PM com.worklight.common.util.jmx.RuntimeMBeanHandler getRMIConnection 
INFO: Establishing RMI connection on localhost with port number 8686 
Jan 14, 2015 4:19:03 PM RuntimeMBeanHandler getRMIConnection() 
FINE: JMXServiceURL = service:jmx:rmi://localhost:8686/jndi/rmi://localhost:8686/jmxrmi 
+0

서버에서 로그 추가 –

답변

0

: 아래

은 catalina.out의 70 개 라인 마지막이다.

현재 URL은 다음과 같습니다 톰캣가 방화벽 뒤에 사용되며, 어떤 경우에 포트 번호 (8686)가 동일 할 수 없습니다 때
JMXServiceURL = service:jmx:rmi://localhost:8686/jndi/rmi://localhost:8686/jmxrmi

위의 구문이 사용됩니다.

Worklight는 JNDI 특성 "ibm.worklight.admin.rmi.serverPort"가 server.xml 파일에 정의 된 경우 위 구문을 사용합니다. 방화벽을 사용하지 않는 경우이 속성 을 제거해야합니다..

는 다음 문서 주제에 따라 자신의 구성을 확인 : http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_optional_config_app_server_tomcat.html

+0

프로젝트 런타임은 서버 구성 도구를 사용하여 작성되었으며 JNDI 특성 "ibm.worklight.admin.rmi.serverPort"를 추가하지 않았습니다. –

2

나는 IBM과 함께 PMR을 열었다. MobileFirst v6.3 이전 버전에서는 페도라 리눅스 (Red Hat 6, 필자의 경우)와 Windows 2012의 특정 구성에이 문제가 있습니다. Tomcat이 MobileFirst 런타임으로 시작/재시작 할 때 Tomcat HTTP 서비스가 시작되지 않았습니다. 설치. v6.3의 최신 iFix가이 문제를 해결했습니다. Windows 2008 또는 Redhat 7에서는 문제가되지 않습니다.

+0

PMR 번호가 있습니까? – wilco

+0

여기에 u : 74374,49R, 000 –